-
Notifications
You must be signed in to change notification settings - Fork 333
Revert RUBY_MAJOR refactoring for 3.0 #447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tianon This made our
RUBY_MAJORenv var we're relying on in our Dockerfile vanish. We're using this env var for setting theBUNDLE_BIN_PATH(e.g.vendor/bundle/ruby/3.1.0/...). So we were using ruby 3.1.4 and now with 3.1.5, the BUNDLE_BIN_PATH becamevendor/bundle/ruby/.0. Sure, I can workaround this, but the change seems wrong and it might affect others!There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the implementation is a bit weird anyway, we thought
RUBY_MAJOR(that is 3.0, 3.1, 3.2. 3.3 ...) has some kind of significance in any RUBY_VERSION (e.g. 3.1.4 or 3.1.5)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the breakage, but it is a variable we never intended to expose (and with a name that isn't really accurate for what it is).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
didn't know and who else might not know it. we're deploying a fix right now. thanks