chore(deps): lock file maintenance #197
Conversation
6346667 to
b895dd9
Compare
|
|
||
| nuxt-component-meta@0.14.1: | ||
| resolution: {integrity: sha512-Q8NuynMJleiutBx4cD33TLp5HCGGmGfz/dE+PNOsAScSAG54hmpPk2beeIwh2VZJoMzPAyPPAqbsdIKpMcOHbA==} | ||
| nuxt-component-meta@https://pkg.pr.new/nuxt-component-meta@e3eb2c4: |
There was a problem hiding this comment.
The lock file pins nuxt-component-meta to a temporary PR build URL (https://pkg.pr.new/nuxt-component-meta@e3eb2c4) instead of a published npm package version. This URL may expire and is not suitable for production deployments.
View Details
Analysis
Lock file pins nuxt-component-meta to expired PR build URL
What fails: pnpm-lock.yaml contains nuxt-component-meta@https://pkg.pr.new/nuxt-component-meta@e3eb2c4 with tarball URL returning 404 Not Found
How to reproduce:
curl -I https://pkg.pr.new/nuxt-component-meta@e3eb2c4
# Returns: HTTP/2 404Result: Lock file contains unreliable dependency source. While pnpm currently falls back to npm registry (v0.14.0 exists), this creates uncertainty in dependency resolution and may fail in environments with stricter registry policies.
Expected: Lock file should reference stable npm registry URLs, not temporary PR build URLs from pkg.pr.new which are designed for preview/testing only
This PR contains the following updates:
🔧 This Pull Request updates lock files to use the latest dependency versions.
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.