chore: cherry pick fixes for rc

[octavian-snyk]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

Where should the reviewer start?

How should this be manually tested?

What's the product update that needs to be communicated to CLI users?

[snyk-io]

✅ 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]

	Warnings
⚠️	Please make changes to snyk help text in Gitbook. Changes will be automatically synchronised to Snyk CLI as a scheduled PR. For more information, see: help/README.md.
⚠️	There are multiple commits on your branch, please squash them locally before merging!

Generated by 🚫 dangerJS against 3ae62df

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Broken NPM Authentication 🔴 [critical] The upload_npm function no longer authenticates the NPM session. The previous npm config set command using HAMMERHEAD_NPM_TOKEN was removed, but it was not replaced with any logic to use the new NPM_ID_TOKEN. Furthermore, npm publish does not automatically recognize NPM_ID_TOKEN. This will result in 401 Unauthorized errors during the NPM publishing phase of the release pipeline. if [ "${DRY_RUN}" == true ]; then echo "DRY RUN: uploading to npm..." npm publish --dry-run ${npm_tag_arg} ./binary-releases/snyk-fix.tgz npm publish --dry-run ${npm_tag_arg} ./binary-releases/snyk-protect.tgz npm publish --dry-run ${npm_tag_arg} ./binary-releases/snyk.tgz else echo "Uploading to npm..." npm publish ${npm_tag_arg} ./binary-releases/snyk-fix.tgz npm publish ${npm_tag_arg} ./binary-releases/snyk-protect.tgz npm publish ${npm_tag_arg} ./binary-releases/snyk.tgz fi Style Violation 🟡 [minor] The new test file uses CommonJS require() syntax to load fs, os, and path. The project's style guide defined in AGENTS.md explicitly requires the use of ES6 import/export for all .ts files to maintain consistency during tooling unification. const fs = require('fs'); const os = require('os'); const path = require('path');

📚 Repository Context Analyzed This review considered 38 relevant code sections from 13 files (average relevance: 0.92) CONTRIBUTING.md (3 segments, lines 231-407) dangerfile.js (lines 1-111) package.json (lines 1-229) help/cli-commands/code.md (lines 1-14) cliv2/pkg/core/main.go (lines 1-220) help/cli-commands/container.md (lines 1-16) package-lock.json (lines 19727-19949) ... and 6 more file(s)

🤖 Repository instructions applied (from AGENTS.md)