docs(release): draft-first publish ordering for a two-channel version - #987
Merged
Conversation
…el version Neither release doc said when the shared GitHub Release may publish. Published release assets are immutable (v1.18.0 burned its tag on exactly this), and the appliance artifacts are built, battery-tested and attached by hand after the DIY stage — so a non-draft publish before they land bricks the shared-release model. releasing.md step 8 now mandates --draft for a two-channel version; appliance-release.md step 5 attaches to the still-draft release and publishes once. Also anchors the appliance cut to the DIY doc's branch mechanics — its step 1 said 'develop is green' while the cut runs from main. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Review catch: release.sh pushes the git tag before creating the draft release, and the v* ruleset blocks re-pointing a pushed tag — so a hardware-battery failure after the DIY cut still spends the version even under --draft. Say so, and say the consequence: start the DIY stage only when the appliance tree is believed final. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Gap found by the 2026-08-14 repo audit while sketching the v2 cut: neither release doc states when the shared GitHub Release may publish, and the two-channel flow makes the ordering load-bearing.
.img/.raucbare built, hardware-battery-tested, and attached by hand after the DIY stage completes.releasing.md step 8 now mandates
release.sh --draftfor a two-channel version (the flag already exists —scripts/release.sh:29); appliance-release.md step 5 attaches to the still-draft release and publishes once, and its cut section now anchors to the DIY doc's branch mechanics (its step 1 said "developis green" while the cut actually runs frommain).Doc-only.
make lint-docs-voiceandmake lint-mdpass.🤖 Generated with Claude Code