Repository navigation
fix(deps): depend on @vercel/nft ^1.11.0 - #9
Open
BleedingDev wants to merge 2 commits into
Open
BleedingDev wants to merge 2 commits into
BleedingDev wants to merge 2 commits into
Conversation
The exact 0.29.2 pin keeps every consumer on an nft release that is more than a year old and forces them to override or patch the transitive dependency to pick up tracing fixes. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why the change
ndepe's exact nft pin keeps consumers on an older release, so this upgrades to nft 1.x and allows compatible updates through a caret range.
Special things to note
Change outline
{ + "engines": { "node": ">=20" }, "dependencies": { - "@vercel/nft": "0.29.2", + "@vercel/nft": "^1.11.0", } }