Repository navigation
Release 1.20.1: publish to npm with trusted publishing - #58
Merged
Merged
Conversation
The release workflow authenticated with an NPM_TOKEN secret, which expires. It now uses npm trusted publishing (OIDC): each package's settings on npmjs.com trust Autter-dev/autter-runtime's release.yml, so no token is stored. The token check step, registry-url and NODE_AUTH_TOKEN are gone; npm is updated to 11 (trusted publishing needs 11.5.1 or newer) before the publish loop. Every public package gets a patch bump with no code changes, so each one publishes through its new trusted publisher within npm's 2-day window: runtime-browser 1.8.2, runtime-node 1.16.1, runtime-edge 1.4.3, runtime-next 1.11.1, runtime-cli 1.4.1, otlp-ingester 1.18.1. docs/RELEASING.md describes the one-time setup per package. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Why
The release workflow publishes with an
NPM_TOKENsecret. npm caps publish tokens' lifetime and is restricting tokens that bypass 2FA for direct publishing, so the next expiry would block a Runtime release the way it blocked CLI 3.10.0 on npm. The CLI moved to trusted publishing in Autter-dev/autter-cli#106 and published 3.10.1 that way.What changes
release.ymlauthenticates with npm trusted publishing (OIDC). The token-check step,registry-urlandNODE_AUTH_TOKENare removed;npm install -g npm@11runs before the publish loop (trusted publishing needs npm 11.5.1+, Node 22 ships npm 10). It already ran onubuntu-latestwithid-token: write.docs/RELEASING.mddescribes the per-package setup instead of the token.Order (do not tag before step 1)
Autter-dev/autter-runtime, workflowrelease.yml, no environment, Allownpm publishticked.otlp-ingesterversion change redeploys the hosted ingester with the same code, reporting 1.18.1.v1.20.1; the Release workflow publishes all six.NPM_TOKENsecret.🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.