docs: release process executable without downstream access - #26
Merged
Conversation
Documents the gate substitution used for v0.3.0: when the downstream repo isn't reachable (e.g. an agent session scoped to this repo), this repo's CI on the candidate commit plus a local render verification gates the release, and the downstream export and tag recording follow as post-release verification. Step 7 now authors notes in gitignored tmp/ and uses --notes-file (heredocs choke on backticks), states the expected notes structure, and adds post-create verification (tag target and a fresh copier copy resolving the tag). https://claude.ai/code/session_01T3RGHgchJZBpvuiesrrE7X
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
2 participants
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.
Documents the release path used to cut v0.3.0, so the process in
updating.mdis fully executable by an agent working only in this repo:simple-modern-uv-templaterepo isn't reachable (e.g. an agent session scoped to this repo), this repo's CI on the candidate commit plus a local render verification gates the release; the downstream export and tag recording (Steps 4–6, 8) follow as post-release verification, with fix-forward via a patch release if they fail.tmp/and usegh release create --notes-file(heredocs choke on backticks and$); states the expected notes structure (theme summary, features/improvements, upgrading note, new question keys with defaults, validation statement, compare link); adds post-create verification — tag target check and a freshcopier copy gh:jlevy/simple-modern-uvresolving the new tag as_commit.This is exactly the procedure followed for v0.3.0.
https://claude.ai/code/session_01T3RGHgchJZBpvuiesrrE7X
Generated by Claude Code