Add release automation + tighten enforce-main-source against forks#1
Merged
Conversation
When a vX.Y.Z tag is pushed, create a GitHub Release with auto-generated notes. Version 0.x.x tags are marked as pre-releases; 1.x.x+ as full releases. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Adds a head-repo check so PRs from forks (where the contributor named their branch 'staging') don't pass the source-branch gate. Combined with the collaborator list controlling who can push to this repo's staging, this restricts main merges to repo-write-access only. Co-Authored-By: Claude Opus 4.7 (1M context) <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.
Two related infra additions for the staging→main flow:
release.yml— when avX.Y.Ztag is pushed, automatically create a GitHub Release with auto-generated notes. Version 0.x.x tags are pre-releases; 1.x.x+ are full releases.enforce-main-source.ymltightening — also rejects PRs from forks. Previously the workflow would pass if a fork named their branchstaging; now the head-repo must equal this repo. Combined with the collaborator list (only repo write-access can push to this repo's staging), this restricts main merges to people the maintainer has explicitly added.Test plan
check-source-branchpasses (PR source IS staging in this repo)