chore: resync root package-lock (fix npm ci on main)#163
Merged
Conversation
npm ci failed on main ("lock file's @types/node@25.9.3 does not satisfy 25.9.5")
because the root lock drifted from the file:./sdk dependency tree. Regenerate it
with npm install; no package.json version changes. Verified locally: npm ci, the
sdk build, typecheck, and the Next.js build all pass.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
npm ciwas failing on main (@types/node@25.9.3in the lock vs25.9.5required by thefile:./sdktree), which is why CI has been red since #149. Regenerated the lock withnpm install(no package.json version changes). Verified locally: npm ci, sdk build, typecheck, and the Next.js build all pass.