fix(release): restore npm upgrade for OIDC trusted publishing#41
Merged
Conversation
Node 22 ships npm 10.x, which can sign provenance but cannot perform the OIDC trusted-publishing registry auth added in npm 11.5.1. Without it, publish falls back to an empty token and 404s. #33 removed this step as 'redundant' — it was load-bearing. Restore it.
Lets a maintainer publish a version whose package.json bump already merged but whose triggered release run failed (e.g. 0.5.7). The version-changed check still guards against republishing.
teallarson
approved these changes
Jul 7, 2026
This was referenced Jul 7, 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
2 participants
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
Publishing
@arcadeai/create-agentto npm has been failing with a 404:The registry is stuck at
0.5.5;0.5.6and0.5.7both failed to publish.Root cause
The package publishes via npm OIDC Trusted Publishing (no token in the workflow). The Trusted Publisher config on npm is correct, and the GitHub OIDC identity matches (
repo:ArcadeAI/create-arcade-agent:environment:npm,release.yml@refs/heads/main) — provenance signing succeeds.But OIDC trusted-publishing registry auth requires npm ≥ 11.5.1, and
setup-nodewithnode-version: 22installs npm 10.x. npm 10.x can sign provenance (Fulcio, since npm 9.5) but cannot authenticate to the registry via OIDC — so it falls back to an empty token and 404s.PR #33 removed
npm install -g npm@latestas "redundant." It was load-bearing. History confirms it: versions published fine under #25 (npm upgrade present); the first CI release after #33 (0.5.6) failed.Changes
npm install -g npm@latestbefore publish so npm can do the OIDC exchange.workflow_dispatchso this can be triggered manually — needed here because0.5.7'spackage.jsonbump already merged tomain, so thepaths: [package.json]trigger won't fire again.After merge
Run the Release workflow manually (Actions → Release → Run workflow on
main). The "Check if version changed" step compares local0.5.7against the registry's0.5.5and will publish0.5.7.