Repository navigation
Conversation
Publish on release:published so the npm trusted publisher keyed on release.yml can be used, drop NODE_AUTH_TOKEN in favour of id-token: write (OIDC), run on Node 24 with npm@latest (trusted publishing needs npm >= 11.5.1), check out the release tag without persisted credentials, keep the explicit build-ts step. GitHub pre-releases go to the beta dist-tag. Co-Authored-By: Claude Fable 5.1 <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. |
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The nonexistent actions/checkout@v7 and actions/setup-node@v7 references prevent the workflow from running.
Review effort: Balanced
Findings: None
What changed in this PR
Migrates npm releases from token authentication to OIDC trusted publishing.
Changes:
- Publishes on release publication using Node 24 and OIDC.
- Routes prereleases to
betaand stable releases tolatest. - Disables persisted checkout credentials.
| File | Description |
|---|---|
.github/workflows/release.yml |
Updates the npm publishing workflow. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Refuse to publish when the release tag is not "v" + the package.json version, so a tag cut on the wrong commit cannot publish an older version under a newer tag. The tag reaches the check through an env variable, never through a shell line. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e.yml github-release.yml created the GitHub release with GITHUB_TOKEN on every version bump pushed to master. Events raised by that token do not start other workflows, so with publishing on release: published a bot-created release would never run release.yml and npm would silently miss the version. Releases are created by a person instead (as since v1.1.3), and release.yml now attaches the npm pack tarball after a successful publish. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Regenerated package-lock.json (clean npm install); no package.json change. qs 6.15.3 -> 6.16.0 (via body-parser) Fixes SNYK-JS-QS-19432017 and SNYK-JS-QS-19432019 Snyk: 2 medium findings -> 0 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
amit-kanswal-cs
approved these changes
Oct 14, 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.
Problem
release.ymlpublishes@contentstack/webhook-listenerto npm with a long-livedNPM_TOKEN.The SE1 publishing policy requires OIDC trusted publishing instead: no token, a
release.ymlworkflow that runs when a release is published, Node 24.Fix
release.ymlis rewritten in place. What changes inside it:release: createdrelease: publishedNPM_TOKENid-token: write, no tokennpm publish --tag latest --access publicnpm publish --access public; pre-releases go to thebetadist-tag, releases tolatestnpm run build-tspersist-credentials: falsecheckout@v4,setup-node@v4@v7v+ thepackage.jsonversiongithub-release.ymlwhen it created the releaseupload-release-assetjob inrelease.yml, after a successful publish (npm pack)github-release.ymlGITHUB_TOKENon every version bump pushed tomasterrelease.yml; releases are created by a personVerification
Node 22 and Node 24: install, build and
npm packall pass.