dep: Add native Ruby 4 support, drop Ruby 3.1 support (v1.19.x)#3592
Merged
flavorjones merged 10 commits intov1.19.xfrom Dec 28, 2025
Merged
dep: Add native Ruby 4 support, drop Ruby 3.1 support (v1.19.x)#3592flavorjones merged 10 commits intov1.19.xfrom
flavorjones merged 10 commits intov1.19.xfrom
Conversation
239b631 to
75e33f5
Compare
Member
Author
|
Seeing segfaults in CI on darwin + ruby4 that I can reproduce locally: Investigating. |
Member
Author
|
Ah, I think the darwin issue is because the darwin linker hack was not being applied, I needed to change |
0d2c153 to
e57c888
Compare
rdoc is omitted from the Gemfile in CI
b882cc8 to
d0efc55
Compare
- Add Ruby 4.0 - Drop Ruby 3.1 - alpine: Bump to 3.23 and add yaml-dev - Bump host ruby to 3.4 - Rubocop target version 3.2, and associated style changes
- Drop Ruby 3.1 (required ruby version is now `>=3.2`)
- Bump some dev dependencies along the way
- Bump macos runners to macos-15{-intel}
- Re-enable sanitize test
- Make sure the darwin linker hack applies in Ruby 4
because JRuby 9.4 =~ Ruby 3.1 for which we're dropping support. Bump rake-compiler-dock to v1.11.1.
Note we have to jump through some new hoops to use bundler in test-gem-install because ruby's bundled minitest is still v5 and we want to be explicit about using v6. Also note, we need to install build-essentials into the JRuby containers to compile prism, which is a dependency of MT6.
It's not clear to me why this is failing, but it seems like the ZLIB_ENABLED flag is set at compile time and then the library refuses to decompress. Not sure if it's an msys issue or what, but I don't have time right now to investigate.
d0efc55 to
f8c8f74
Compare
flavorjones
added a commit
that referenced
this pull request
Dec 28, 2025
**What problem is this PR intended to solve?** #3590, bumping some other dev dependencies along the way Note that this is a forward-port of #3592 to `main` **Have you included adequate test coverage?** Existing coverage is adequate. **Does this change affect the behavior of either the C or the Java implementations?** No functional changes.
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
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.
What problem is this PR intended to solve?
#3590, bumping some other dev dependencies along the way
Note that this will be the first release of v1.19.x which is an extension of v1.18.x.
Have you included adequate test coverage?
Existing coverage is adequate.
Does this change affect the behavior of either the C or the Java implementations?
No functional changes.