Add a .ruby-version file #2130
Merged
Add a .ruby-version file #2130
+1
−6
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
In two recent pull requests, new contributors have had CI failing because they used Ruby 3.3 (or older) to run the documentation Rake tasks. (Ruby 3.4 formats hashes a bit differently, adding whitespace around hashrockets.) By adding a .ruby-version file, most contributors will automatically be using the same Ruby version. Ideally we would not need to specify the patch version in .ruby-version, but I believe that the `major.minor.patch` format is what is compatible with the most Ruby version managers out there. I found this discussion about writing a specification for .ruby-version, but it doesn't seem to be completed yet: ruby/rubygems#7074
ydah
approved these changes
Nov 6, 2025
Member
|
Thank you! |
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.
In two recent pull requests, new contributors have had CI failing because they used Ruby 3.3 (or older) to run the documentation Rake tasks. (Ruby 3.4 formats hashes a bit differently, adding whitespace around hashrockets.)
By adding a .ruby-version file, most contributors will automatically be using the same Ruby version. Ideally we would not need to specify the patch version in .ruby-version, but I believe that the
major.minor.patchformat is what is compatible with the most Ruby version managers out there.I found this discussion about writing a specification for .ruby-version, but it doesn't seem to be completed yet: ruby/rubygems#7074