Skip to content

fix(deps): restore platform-specific optional packages in package-lock.json - #270

Merged
Harshi-Shah-CS merged 1 commit into
developmentfrom
CL-0000
Oct 30, 2026
Merged

Harshi-Shah-CS merged 1 commit into
developmentfrom
CL-0000

Conversation

@Harshi-Shah-CS

Copy link
Copy Markdown
Contributor

Summary

The v1.11.4 publish workflow (run 41013814593) failed at npm ci, so the release never reached npm publish and npm is still on 1.11.3.

npm 11 (Node 24 in the release job) rejected package-lock.json as out of sync with 50 missing entries: the per-platform builds of rollup and @unrs/resolver-binding, such as @rollup/rollup-linux-x64-gnu. npm 10 tolerates the gap, and no PR check runs npm ci, so it went unnoticed. #226 had restored these entries on main, but the main → development sync for this release (#264) kept development's lockfile and dropped them.

Change

  • Regenerated package-lock.json with npm install --package-lock-only on npm 11.
  • The change only adds the 50 missing entries: no package is removed or re-versioned, and package.json is unchanged.

Verification

  • npm ci --dry-run passes on npm 10 and npm 11.
  • On npm 11, a clean npm ci, then npm run prepack, then npm pack --dry-run produces @contentstack/cli-launch@1.11.4 with 102 files.
  • npm test passes: 139 unit and 31 integration tests.

After merge

Promote development → staging → main. Then move the v1.11.4 tag and release to the new main commit and publish it again. Re-running the failed run would build the old tag commit.

#claude_code#
🤖 Generated with Claude Code

…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>
@Harshi-Shah-CS
Harshi-Shah-CS requested a review from a team as a code owner October 30, 2026 09:25
@snyk-io

snyk-io Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues
✅ Licenses 0 0 0 0 0 issues
✅ Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@github-actions

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 10 25 ✅ Passed
🟡 Medium Severity 0 2 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ 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:

  • Critical without fixes: 0
  • High without fixes: 10
  • Medium without fixes: 2
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants