Repository navigation
docs: keep Releasing to what contributors need - #7
Merged
Merged
Conversation
Contributors add a changeset; the maintainers' release, re-tag and bootstrap steps move to the maintainers' docs. The trusted publishing and provenance facts stay.
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.
The maintainers' release steps now live in the maintainers' own docs. This repo keeps what an outside contributor can use.
pnpm changeset) for user-visible changes.pnpm releaseand its steps, the failed-release re-tag recipe, and the bootstrap / Trusted Publisher settings.No code or workflow changes;
pnpm releaseandrelease.ymlare unchanged.