Drop Ruby 3.1 support; automate release process #92
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
gjtorikian
added a commit
that referenced
this pull request
Dec 19, 2025
Drop Ruby 3.1 support; automate release process
Merged
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.
This PR closes #79.
Right now the
cross_compile.ymlhas one purpose: to build the gem and store the resulting artifact. This happens on every push. The entire point of it is to provide a place forscript/releaseto fetch the gem and publish it to RubyGems.To me, there are two problems:
script/releasemanually, a cumbersome process, because the script depends on finding the latestrun-idto fetch the right artifactsI want to move everything over to OIDC trusted publishing which uses short-lived tokens.
I have a set of workflows in my personal repositories that I use to streamline publishing. So, I'm migrating the release workflow here to using that. Additionally, the
build.ymlworkflow already attempts to compile the gem, so we're not losing any validation of the build by removingcross_compile.yml.Lastly, I noticed that the gem was available for Ruby 3.1, but wasn't actually compiling for it. Since 3.1 has been EOL for a while, I updated the gemspec.