ci(release): land releases on lightly-protected main (drop PAT)#13
Merged
Conversation
Mirror the NoiXdev/inventorix model: the release bot pushes the CHANGELOG to `main`, which is only lightly protected (deletion + non-fast-forward + linear-history, no PR/status-check rules), so the default GITHUB_TOKEN can push it directly — no RELEASE_TOKEN PAT and no bypass actor. - release.yml: checkout/commit/push CHANGELOG to main via GITHUB_TOKEN - add protect-main ruleset (scripts/main-ruleset.json + applier) - develop stays the strict, PR + CI gated integration branch Release ritual: merge develop -> main (squash/linear), tag on main.
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.
Adapts the NoiXdev/inventorix model so releases work with no PAT.
Why
inventorix avoids a release token by pushing its changelog to a branch (
main) whose ruleset has onlydeletion+non_fast_forward+required_linear_history— no PR/status-check rules — so the defaultGITHUB_TOKENcan push a normal linear commit directly. The strict PR gate lives ondevelop, where nothing auto-pushes.Changes
release.yml— changelog job now checks out and pushes tomainwith the defaultGITHUB_TOKEN; theRELEASE_TOKENPAT is removed.scripts/main-ruleset.json+apply-main-ruleset.sh— the newprotect-mainruleset (already applied live, id17589891).apply-develop-ruleset.sh— comment updated (develop no longer receives auto-pushes).developkeeps its strictprotect-developruleset unchanged.New release ritual
develop → main(squash/linear merge to satisfyrequired_linear_history).main(vX.Y.Z).mainviaGITHUB_TOKEN, and builds the installers.No
RELEASE_TOKENsecret required — you can delete it if you created one.