ci(stackblitz): regenerate package-lock.json for TypeScript 7 (unblocks main) - #556
Merged
Merged
Conversation
#439 bumped package.json to typescript ^7.0.2 and updated pnpm-lock.yaml, but the StackBlitz demo boots from package-lock.json, which still pinned 6.0.3. The 'Check the StackBlitz npm lockfile is in sync' step therefore fails on main itself, and every open PR inherits the failure since the check runs against the merge result. Regenerated with the exact command the check prints: d=$(mktemp -d) && cp package.json "$d" \ && (cd "$d" && npm install --package-lock-only --ignore-scripts) \ && cp "$d/package-lock.json" . check-stackblitz-lock.mjs now reports 'package-lock.json is in sync with package.json (v3)'. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
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.
Description
mainis currently failing CI, and so is every open PR — the failure is inherited, not caused by them.Reproduced on a clean checkout of
mainate1676fed:package.jsondeclares"typescript": "^7.0.2"whilepackage-lock.jsonstill pins6.0.3.Root cause
#439 (dependabot, TypeScript 6.0.3 → 7.0.2) updated
package.jsonandpnpm-lock.yaml— the files pnpm uses — but notpackage-lock.json, which is what the StackBlitz demo boots from. The repo keeps both on purpose: pnpm for development, npm for the WebContainer demo. Dependabot only knows about one of them.Because the sync check runs against the merge result, every open PR now shows a red
Build and Testfor a file it never touched.Changes
Regenerated
package-lock.jsonwith the exact command the check prints on failure:Lockfile only — no source, no config, no dependency ranges changed.
Verification
Type of Change
Checklist
package.jsonranges changed — the lockfile now simply matches themFollow-up to #439.