Repository navigation
VS Code extension: regenerate package-lock.json so the 0.2.0 publish works - #112
Merged
Merged
Conversation
….0 publish work The publish workflow's `npm ci` failed with EINTEGRITY for tmp, qs, linkify-it and serialize-javascript. Their lockfile entries named newer versions (0.2.6, 6.16.0, 5.0.2, 7.0.3) but carried the integrity hashes of older ones (0.2.5, 6.15.2, 5.0.1, 6.0.2): versions had been edited by hand without re-resolving. The same kind of edit left markdown-it at 15.0.3 under @vscode/vsce, whose range is ^14.1.0 and whose own linkify-it ^6.1.0 was never installed, so `vsce package` failed with "linkify_it.LinkifyIt is not a constructor" even with the hashes fixed. The other 503 entries' hashes matched the registry. Regenerated from package.json with `npm install --package-lock-only`, so every entry is npm's own resolution within the declared ranges. Verified with a clean `npm ci` (every tarball checked against its hash), tsc, eslint, the mocha tests, `npm run package` (autter-vscode-0.2.0.vsix), and `npm audit --omit=dev` (0 vulnerabilities). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TtUpr8sH39LAcxNTh4QreC
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
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.
The publish run for the VS Code extension 0.2.0 (from #110) failed at
npm ciwithEINTEGRITY. This PR regenerates the extension's lockfile so it installs and packages.What was wrong
Four lockfile entries named newer versions but carried the integrity hashes of older ones, which suggests versions were edited by hand without re-resolving:
The same kind of edit left
markdown-itat 15.0.3 under@vscode/vsce, whose range is^14.1.0. That version needslinkify-it^6.1.0, which was never installed, sovsce packagefailed withlinkify_it.LinkifyIt is not a constructoreven after fixing the hashes.The other 503 entries' hashes matched the npm registry's metadata. Every
resolvedURL points at registry.npmjs.org, so the bad hashes could only make installs fail, not swap in other code.Fix
Regenerated
agent-support/vscode/package-lock.jsonfrompackage.jsonwithnpm install --package-lock-only. Every entry is now npm's own resolution within the declared ranges.package.jsonis unchanged.Testing
npm cipasses, with every tarball checked against its hash.tsc,eslintand the mocha tests (11) pass.npm run packagebuildsautter-vscode-0.2.0.vsix, which includes the new findings code.npm audit --omit=dev: 0 vulnerabilities.After merge, I'll dispatch the publish workflow on
main(it publishes thepackage.jsonversion, 0.2.0).Generated by Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.