chore: switch npm release to Trusted Publishing (OIDC), matching @gethelio/proxy#21
Merged
Merged
Conversation
…helio/proxy Replace the long-lived NPM_TOKEN (granular, bypass-2FA, @gethelio-scope) with tokenless OIDC trusted publishing, mirroring the proxy package's release.yml: - run the publish job under `environment: npm` with `id-token: write` - add "Upgrade npm for trusted publishing" (npm@latest) for OIDC support - publish via `npm publish --access public` (was `pnpm publish` + NODE_AUTH_TOKEN) - drop the NODE_AUTH_TOKEN env entirely Provenance is generated automatically by the OIDC publish. The tag↔version guard and the prepublishOnly verify gate are unchanged. Prereq before the next release: configure this repo + workflow (environment `npm`) as a Trusted Publisher on the @gethelio/helio-openclaw npm package settings. After the next release confirms OIDC works, the NPM_TOKEN secret can be deleted and the helio-openclaw-release-ci token revoked.
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.
Migrates this repo's release auth from the long-lived
NPM_TOKENto tokenless OIDC Trusted Publishing, mirroring@gethelio/proxy'srelease.yml(verified: proxy publishes via OIDC underenvironment: npm, no stored token).Changes to
release.ymlenvironment: npmwithpermissions: id-token: writenpm install -g npm@latest)npm publish --access public(waspnpm publish --no-git-checks+NODE_AUTH_TOKEN)NODE_AUTH_TOKENenv entirelyProvenance is generated automatically by the OIDC publish. The tag↔version guard and the
prepublishOnlyverify gate are unchanged. Trigger is stillv*tags only.Configure the Trusted Publisher on npm before tagging the next version, or the publish will fail:
@gethelio/helio-openclaw→ Settings → Trusted Publisher → GitHub Actionsgethelio/helio-openclawrelease.ymlnpmThis PR is inert until then (it only runs on a tag, and
0.1.0is already out).Cleanup after the next successful OIDC release
NPM_TOKENrepo secrethelio-openclaw-release-cinpm tokenformat:checkclean (validates the workflow YAML).