Skip to content

Add JRuby 10.0.0.1 and 9.4.12.1 #2530

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

Merged
merged 2 commits into from
May 7, 2025
Merged

Conversation

headius
Copy link
Contributor

@headius headius commented May 7, 2025

This adds JRuby 10.0.0.1 and 9.4.12.1, which include the jruby-openssl fix for GHSA-72qj-48g4-5xgx.

@@ -0,0 +1,2 @@
require_java 8
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this require a newer Java version? 4cdc5a7

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have fixed that and re-pushed, but where does this come from? I just used the update script. Does it look at the current Java in PATH and somehow use that?

@mislav
Copy link
Member

mislav commented May 7, 2025

I've based this on the 10.0.0.0 PR, which I saw today has not yet been merged.

Not sure what you mean, since the 10.0.0.0 PR was merged and released three weeks ago? https://github.com/rbenv/ruby-build/releases/tag/v20250415

@headius
Copy link
Contributor Author

headius commented May 7, 2025

Sorry, I got my repositories crossed.

Yes, should be 21 minimum, I'll fix that. Thanks!

@headius headius force-pushed the jruby-10.0.0.1-9.4.12.1 branch from efe8c35 to 9a4637f Compare May 7, 2025 16:57
@mislav mislav merged commit a45de7c into rbenv:master May 7, 2025
4 checks passed
@headius headius deleted the jruby-10.0.0.1-9.4.12.1 branch May 7, 2025 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants