Repository navigation
ci: Pin release platforms and Ruby versions per branch - #657
Merged
Merged
Conversation
The release workflow always runs from `main`, and builds the platforms and Ruby versions from oxidize-rb's live lists. These change over time, so an older release branch can stop building e.g., release-36's `rb_sys` doesn't support `aarch64-mingw-ucrt`. Release branches and tags can now pin both lists in `.github/release-matrix.json`. `native-gem-matrix.yml` reads the file when asked to, and is now used by CI too, so that a branch is tested against the Ruby versions it releases for. This is only applicable for release branches, main keeps using whatever is pulled from fetch ci data.
saulecabrera
requested review from
jacobsteves and
jeffcharles
and removed request for
jeffcharles
October 15, 2026 00:27
jacobsteves
approved these changes
Oct 15, 2026
saulecabrera
enabled auto-merge (squash)
October 15, 2026 00:34
saulecabrera
disabled auto-merge
October 15, 2026 12:41
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.
The release workflow always runs from
main, and builds the platforms and Ruby versions from oxidize-rb's live lists. These change over time, so an older release branch can stop building e.g., release-36'srb_sysdoesn't supportaarch64-mingw-ucrt.Release branches and tags can now pin both lists in
.github/release-matrix.json.native-gem-matrix.ymlreads the file when asked to, and is now used by CI too, so that a branch is tested against the Ruby versions it releases for. This is only applicable for release branches, main keeps using whatever is pulled from fetch ci data.