Backdating to Ruby 3.2.7 (SCP-5959) #34
Closed
Conversation
This file contains 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
|
This may not be necessary - local installation issue could be specific to my machine due to updates to |
|
Closing as issue was solely on my machine - |
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.
BACKGROUND & CHANGES
This backdates our Ruby version to 3.2.7. While the newest supported version of 3.4.2 works inside Docker, installing updated gems locally fails for several gems that no longer have any supported updates. Attempting to migrate to other gems is a very large undertaking, so going back to Ruby 3.2.x is more palatable.
MANUAL TESTING
See this build for verification that 3.2.7 works with the base image. A forthcoming PR in single_cell_portal_core will verify that 3.2.7 works both inside and outside Docker.