ci: retire master branch — point release workflow and docs at main#80
Merged
Conversation
The master branch was retired on GitHub; the release workflow still triggered on master, so release automation had been dead since ~0.0.34 (missing tags 0.0.36-0.0.38). Repoint release.yml push/pull_request triggers to main, and drop the `v` tag prefix to match current tag practice (0.0.39, 0.0.40 are unprefixed). Also update Contributor-Guide docs that still referenced master.
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.
Summary
The
masterbranch was retired on GitHub (onlydevelop,main, and feature branches remain). However the release workflow and several docs still referenced it.release.yml: triggered only onmaster— a branch that no longer exists — so release automation has been dead since ~0.0.40. Repointedpushandpull_requesttriggers tomain.vprefix inrelease.yml(tag-existence check, tag creation, and theaction-gh-releasetag_name/name). Recent real tags are unprefixed (0.0.39,0.0.40); the workflow'sv-prefixed format would have produced an inconsistentv0.0.xtag.doc/Contributor-Guide/files that still described merging tomaster.Effect
Once this reaches
main, a version-bumped push tomainwill auto-create the tag and GitHub Release again — no manual tagging.Test plan
main, confirm the "Create Release" workflow fires on the next release push