[ruby] Update Gem Dependencies#104
Merged
Merged
Conversation
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.
1. concurrent-ruby: 1.3.6 → 1.3.7
Release date: 16 June 2026 · Release notes · Compare v1.3.6...v1.3.7 (14 commits)
This is primarily a security / thread-safety bug-fix release (three Low-severity CVEs).
1-1. Security fixes
AtomicReference#update: Fixed an infinite retry loop / livelock that occurred when the stored value isFloat::NAN.ReentrantReadWriteLock: Fixed a read hold-count overflow that spilled into the write-lock bit after 32,768 reentrant reads.ReadWriteLock: Fixed two issues:-1, blocking all subsequent lock acquisitions.1-2. Infrastructure / other
concurrent-ruby-extcorrectly on Darwin 32-bit systems (#1064).deploy-pagesv4→v5,upload-pages-artifactv4→v5).ReentrantReadWriteLockspecs.Contributors: @eregon, @joshuay03, @barracuda156 (first contribution).
2. Bottom line
AtomicReference/ReadWriteLock/ReentrantReadWriteLock) plus CI/platform housekeeping — safe, recommended bump.