ci(release): publish to npm via trusted publishing on release#57
Closed
Sumit1993 wants to merge 1 commit into
Closed
ci(release): publish to npm via trusted publishing on release#57Sumit1993 wants to merge 1 commit into
Sumit1993 wants to merge 1 commit into
Conversation
…e cuts a release Adapted from prismalens's release.yml: OIDC trusted publishing (no npm token secret, automatic provenance), kept on release-please instead of changesets. Dogfooding moves to the release PR — CI already builds, tests, and smoke-installs the packed tarball there; merging it is the ship decision and now publishes automatically. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ATqpNDpPMsBY9UrSNuvEWw
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.
What
Extends
release-please.ymlwith apublishjob, adapted from prismalens's release.yml: when release-please cuts a release (the release PR merges), the same commit is published to npm via trusted publishing (OIDC) — no npm token secret, provenance attestations generated automatically.Kept release-please (not changesets) since this repo's whole release line (PR-title gate, config, ADRs) is built on it; the prismalens part being adopted is the OIDC publish mechanics.
Why auto-publish is now safe
The old header said publish stays manual for dogfooding. Dogfooding now happens on the release PR itself — CI builds, tests, and smoke-installs the packed tarball on it — so merging the release PR is the ship decision.
Before merging
Register the trusted publisher on npmjs.com: mage-memory → Settings → Publishing access → Trusted publisher → GitHub Actions, repo
Sumit1993/mage-memory, workflowrelease-please.yml, no environment. Without this the publish job fails auth (nothing else breaks).🤖 Generated with Claude Code
https://claude.ai/code/session_01ATqpNDpPMsBY9UrSNuvEWw