chore(deps): update all non-major dependencies #196
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
25b8dc5 to
353d7c7
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
353d7c7 to
f5d967b
Compare
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
Comment on lines
+3859
to
+3861
| nuxt-component-meta@https://pkg.pr.new/nuxt-component-meta@e3eb2c4: | ||
| resolution: {tarball: https://pkg.pr.new/nuxt-component-meta@e3eb2c4} | ||
| version: 0.14.0 |
There was a problem hiding this comment.
The lock file is using an unreleased PR preview version of nuxt-component-meta instead of a published npm package, which will cause deployment and CI/CD failures.
View Details
Analysis
Lock file contains inaccessible pkg.pr.new dependency causing potential CI/CD failures
What fails: pnpm-lock.yaml references nuxt-component-meta@https://pkg.pr.new/nuxt-component-meta@e3eb2c4 which returns HTTP 404
How to reproduce:
curl -I "https://pkg.pr.new/nuxt-component-meta@e3eb2c4"
# Returns: HTTP/2 404Result: Lock file contains 4 references to inaccessible URL that could fail in fresh CI/CD environments
Expected: Lock file should only reference stable, accessible package sources
Fix: Regenerating the lock file with rm pnpm-lock.yaml && pnpm install resolves to working dependencies and removes the problematic pkg.pr.new references entirely
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.2.55->^1.2.56^3.7.1->^3.8.0^1.9.0->^1.10.010.19.0->10.20.0Release Notes
nuxt/content (@nuxt/content)
v3.8.0Compare Source
Features
Bug Fixes
Performance Improvements
nuxt/eslint (@nuxt/eslint)
v1.10.0Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
pnpm/pnpm (pnpm)
v10.20.0Compare Source
Minor Changes
--alloption inpnpm --helpto list all commands #8628.Patch Changes
latestversion doesn't satisfy the maturity requirement configured byminimumReleaseAge, pick the highest version that is mature enough, even if it has a different major version #10100.createcommand should not verify patch info.managePackageManagerVersionstofalse, when switching to a different version of pnpm CLI, in order to avoid subsequent switches #10063.Configuration
📅 Schedule: Branch creation - "on Monday" (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.