docs: document the tokenless release path and add a dry_run to manual-publish [AIS-7539] - #23
Merged
Merged
Conversation
…-publish [AIS-7539] Publishing runs on npm trusted publishing bound to release-please.yml; there are no secrets to rotate and manual-publish.yml cannot authenticate unless that trust is re-pointed. The new dry_run input (default on) makes a manual-publish dispatch a safe proof that checkout, build, version assertion and pack still work from a current maintainer's account.
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.
The release path had no written record and no safe way to exercise it after its only operator left.
Publishing for this package is npm trusted publishing (GitHub Actions OIDC) bound to
release-please.yml; there are no repository or organization secrets in the path, andmanual-publish.ymlhas never run and cannot authenticate whilerelease-please.ymlholds the package's single trusted-publisher slot.What changed:
manual-publish.ymlgains adry_runinput, on by default, that stops before the registry (npm publish --dry-run). Dispatching it against an existing tag is now the way to prove the release path.Risk: none to the automatic path;
release-please.ymlis untouched.How verified
NODE_AUTH_TOKENis setup-node's placeholder and the publish produced a sigstore attestation, i.e. OIDC.manual-publish.ymlis dispatched withref=0.0.2 expected_version=0.0.2 dry_run=trueand the run link goes on AIS-7539.Tracks https://linear.app/speechify-inc/issue/AIS-7539