docs: publish releases via gh release edit, drop stale develop references - #462
Open
Wiesenwischer wants to merge 1 commit into
Open
Wiesenwischer wants to merge 1 commit into
Wiesenwischer wants to merge 1 commit into
Conversation
…nces Document that a release is published by promoting the existing Release-Drafter draft (GitHub UI or 'gh release edit --draft=false') and why 'gh release create' must not be used: the drafter keeps its draft, leaving two same-tag entries that make tag-based edit/delete ambiguous. Also correct claims that no longer hold: there is no 'develop' branch (main is the only permanent one), and the dev image is built on push to 'main' and tagged 'latest', not 'develop' (see .github/workflows/docker-dev.yml).
github-actions
Bot
added
documentation
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.
Why
Follow-up to the v0.82.0 release: the release list briefly held two entries with the same tag — the real release plus the Release-Drafter draft that
gh release createhad left behind. Tag-basedgh release edit/deleteare ambiguous in that state, so cleanup needed the numeric release id.Changes
gh api ... select(.draft==true)→gh release edit <tag> --notes-file … --draft=false --latest) next to the GitHub-UI path, plus a note that the drafter's raw "What's Changed" list is not sufficient as release notes.developreferences removed —mainis the only permanent branch (CLAUDE.md), so PRs come fromfeature/*/bugfix/*, and the hotfix step no longer mentions bypassingdevelop.main(tags ignored) and tags the imagelatest— the doc claimed adeveloptrigger and a:developtag, including in thedocker inspectexample.Docs only — no code, no workflow changes.