Repository navigation
Require Forge 2 binary releases to use master - #5
Merged
mrgh97 merged 1 commit intoNov 18, 2026
Merged
Conversation
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
Build Forge 2 binary releases from
master. Create and push the version tag before dispatch. The workflow validates the branch, matching release version and tag, and that the tagged commit belongs to the branch before compiling.Validation
Parsed the Actions workflow and exercised the Bash guard with valid inputs and with wrong branches, nonspecific refs and wrong major versions. Checked that the current release tag is an ancestor of the intended branch. The published source tag remains immutable.