Repository navigation
ci: plan releases before publishing authentication - #56
Merged
Merged
Conversation
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.
Summary
We now decide whether a release is due before checking publishing credentials. Dry runs can preview a release without npm access.
Details
Testing steps
Run:
pnpm install --frozen-lockfile pnpm test pnpm run lint pnpm run format pnpm run typecheck pnpm run build pnpm run changelog:check pnpm run security:checkAll checks should pass. Dispatch Release with dry-run enabled and confirm it previews v2.0.2 without publishing or creating a tag.
Local logs, security review, SBOM and image proof.