Repository navigation
fix(deps): restore platform-specific optional packages in package-lock.json - #270
Merged
Merged
Conversation
…k.json The v1.11.4 publish workflow failed at `npm ci`: npm 11 (Node 24 in CI) reported 50 packages missing from the lockfile - the per-platform builds of rollup and @unrs/resolver-binding. npm 10 tolerates the gap, so local installs and PR checks never caught it. #226 had restored these entries on main, but the main -> development sync for this release kept development's lockfile and dropped them. Regenerated with `npm install --package-lock-only` on npm 11. The change only adds the missing entries; no package is removed or re-versioned. #claude_code# 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
AryanBansal-launch
approved these changes
Oct 30, 2026
tejas-contentstack
approved these changes
Oct 30, 2026
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.
Summary
The v1.11.4 publish workflow (run 41013814593) failed at
npm ci, so the release never reachednpm publishand npm is still on 1.11.3.npm 11 (Node 24 in the release job) rejected
package-lock.jsonas out of sync with 50 missing entries: the per-platform builds ofrollupand@unrs/resolver-binding, such as@rollup/rollup-linux-x64-gnu. npm 10 tolerates the gap, and no PR check runsnpm ci, so it went unnoticed. #226 had restored these entries onmain, but the main → development sync for this release (#264) kept development's lockfile and dropped them.Change
package-lock.jsonwithnpm install --package-lock-onlyon npm 11.package.jsonis unchanged.Verification
npm ci --dry-runpasses on npm 10 and npm 11.npm ci, thennpm run prepack, thennpm pack --dry-runproduces@contentstack/cli-launch@1.11.4with 102 files.npm testpasses: 139 unit and 31 integration tests.After merge
Promote development → staging → main. Then move the
v1.11.4tag and release to the newmaincommit and publish it again. Re-running the failed run would build the old tag commit.#claude_code#
🤖 Generated with Claude Code