docs: document manual tag step in GITHUB_OPERATIONS.md (#83)#168
Merged
StefanSteiner merged 1 commit intoJun 29, 2026
Merged
Conversation
Add a 'Manual tag step (after release-please PR merge)' subsection covering the deliberate human tag-creation checkpoint (the last point a bad release can be stopped before it ships permanently to crates.io/npm) and the exact gh/git sequence: confirm main at the merge SHA, sanity-check the manifest, extract notes from CHANGELOG.md, create the tag + GitHub Release. Also add options for stopping a release after merge but before tagging, and a README doc-table row linking GITHUB_OPERATIONS.md. Closes tableau#83.
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.
Closes #83. Adds a 'Manual tag step (after release-please PR merge)' subsection — the human tag-creation checkpoint and the exact gh/git sequence —
plus a README doc-table row. Produced via an operator-watched CU (claude-unleashed) harness-writer run.