Upgrade Ruby from 3.2.9 to 3.4.7#6
Merged
Merged
Conversation
Ruby 3.2 reaches EOL on March 31, 2026. Ruby 3.4 is supported through March 2028. This also unlocks native SecureRandom.uuid_v7 (added in Ruby 3.3), which enables time-ordered UUIDs for better database index performance. A follow-up PR can switch ApplicationRecord#assign_uuid to use uuid_v7. Amp-Thread-ID: https://ampcode.com/threads/T-019c7d17-f580-76a7-9ce6-3d6abdf7d9af Co-authored-by: Amp <amp@ampcode.com>
HamptonMakes
approved these changes
Feb 23, 2026
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
2 participants
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.
Why
Ruby 3.2 reaches EOL on March 31, 2026 — just over a month away.
What changed
.ruby-version: 3.2.9 → 3.4.7Dockerfile: updatedRUBY_VERSIONargVerified
bundle installsucceeds with no gem incompatibilitiesUnlocks
Ruby 3.3+ adds native
SecureRandom.uuid_v7, which produces time-ordered UUIDs with better B-tree index performance than the current UUIDv4. A follow-up PR can switchApplicationRecord#assign_uuidto use it: