Skip to content

upgrade jruby to 9.4.12.0 #16986

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

Closed
wants to merge 15 commits into from
Closed

upgrade jruby to 9.4.12.0 #16986

wants to merge 15 commits into from

Conversation

jsvd
Copy link
Member

@jsvd jsvd commented Jan 30, 2025

Important issues addressed:

  • Fixed an issue where Mutex lock acquisition may leave the Mutex locked if an asynchronous Thread interrupt happens at the same time. #8585, #8586
  • Fixed a memory leak where singleton classes would leave behind bookkeeping objects that accumulated over time. #8591, #8598

Depedency upgrades:

  • rubygems been updated to version 3.6.3 to fix an incompatibility with bundler 2.6. #8590, #8596
  • bundler has been updated to version 2.6.3. #8596
  • jruby-openssl has been updated to 0.15.3. #8458, Release 0.15.3
  • jar-dependencies has been updated to 0.5.4 to fix remaining issues loading Maven jars in containerized environments. #8593, #8595

Exhaustive test suite run: https://buildkite.com/elastic/logstash-exhaustive-tests-pipeline/builds/1237

closes #17007

@jsvd jsvd force-pushed the bump_jruby_9_4_11_0 branch from ad296de to 74d5065 Compare February 14, 2025 11:35
@jsvd jsvd changed the title upgrade jruby to 9.4.11.0 upgrade jruby to 9.4.12.0 Feb 14, 2025
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@elasticmachine
Copy link
Collaborator

elasticmachine commented Feb 14, 2025

Copy link
Contributor

mergify bot commented Mar 5, 2025

This pull request does not have a backport label. Could you fix it @jsvd? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
  • backport-8.x is the label to automatically backport to the 8.x branch.

Copy link
Contributor

mergify bot commented Mar 5, 2025

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Mar 5, 2025
Copy link
Contributor

mergify bot commented Mar 5, 2025

This pull request is now in conflicts. Could you fix it @jsvd? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b bump_jruby_9_4_11_0 upstream/bump_jruby_9_4_11_0
git merge upstream/main
git push upstream bump_jruby_9_4_11_0

@donoghuc donoghuc mentioned this pull request Jun 2, 2025
5 tasks
@donoghuc
Copy link
Member

donoghuc commented Jun 2, 2025

I'm taking this over in #17696 . Looks like we got 9.4.12.1 since this began. Going to go ahead and close this one for now. Thanks!

@donoghuc donoghuc closed this Jun 2, 2025
@donoghuc donoghuc mentioned this pull request Jun 2, 2025
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify
Projects
None yet
Development

Successfully merging this pull request may close these issues.

JRuby 9.4.13.0 upgrade
4 participants