ci(release): npm ≥ 11.5.1 so OIDC trusted publishing works#598
Merged
NagyVikt merged 1 commit intoJun 12, 2026
Merged
Conversation
changesets/action detects OIDC (id-token: write is set) when NPM_TOKEN is absent, but Node 20 bundles npm 10.x which cannot do the OIDC exchange — publish died with ENEEDAUTH. Upgrading npm completes the runner side; the npmjs.com side needs colonyq to list opencue/colony + release.yml as a trusted publisher.
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
1 participant
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 Release run on the 0.8.0 commit showed changesets/action choosing npm trusted publishing ('No NPM_TOKEN found, but OIDC is available') — the workflow already grants
id-token: write. It still hitENEEDAUTHbecause Node 20 bundles npm 10.x and the OIDC token exchange needs npm ≥ 11.5.1. This adds one step upgrading npm before install.Remaining (owner-only, no secrets needed): on npmjs.com →
colonyq→ Settings → Trusted Publisher → GitHub Actions with owneropencue, repocolony, workflowrelease.yml. Once set, re-running the Release workflow publishescolonyq@0.8.0with no NPM_TOKEN at all.Test plan
🤖 Generated with Claude Code