chore(deps): update concurrent-ruby requirement from ~> 1.3.0, < 1.3.7 to ~> 1.3.0, < 1.3.8

[dependabot]

Updates the requirements on concurrent-ruby to permit the latest version.

Release notes

Sourced from concurrent-ruby's releases.

v1.3.7

There are 3 security fixes in this release, so updating is recommended. These security vulnerabilities are not very likely to be hit in practice and have a corresponding Low severity score.

What's Changed

• CVE-2026-54904 AtomicReference#update livelocks when the stored value is Float::NAN. Fix by @​joshuay03 and @​eregon
• CVE-2026-54905 ReentrantReadWriteLock read-count overflow grants a write lock without exclusivity. Fix by @​joshuay03
• CVE-2026-54906 ReadWriteLock allows wrong-thread write release and stray read-release counter corruption. Fix by @​joshuay03
• concurrent-ruby-ext: fix build on Darwin 32-bit by @​barracuda156 in ruby-concurrency/concurrent-ruby#1064
• Add SECURITY.md by @​eregon in ruby-concurrency/concurrent-ruby#1104
• Add Ruby 4.0 in CI by @​eregon in ruby-concurrency/concurrent-ruby#1106

New Contributors

• @​barracuda156 made their first contribution in ruby-concurrency/concurrent-ruby#1064

Full Changelog: ruby-concurrency/concurrent-ruby@v1.3.6...v1.3.7

Changelog

Sourced from concurrent-ruby's changelog.

Release v1.3.7 (16 June 2026)

concurrent-ruby:

• See the release notes on GitHub.

Release v1.3.6 (13 December 2025)

concurrent-ruby:

• See the release notes on GitHub.

Release v1.3.5, edge v0.7.2 (15 January 2025)

concurrent-ruby:

• (#1062) Remove dependency on logger.

concurrent-ruby-edge:

• (#1062) Remove dependency on logger.

Release v1.3.4 (10 August 2024)

• (#1060) Fix bug with return value of Concurrent.available_processor_count when cpu.cfs_quota_us is -1.
• (#1058) Add Concurrent.cpu_shares that is cgroups aware.

Release v1.3.3 (9 June 2024)

• (#1053) Improve the speed of Concurrent.physical_processor_count on Windows.

Release v1.3.2, edge v0.7.1 (7 June 2024)

concurrent-ruby:

• (#1051) Remove dependency on win32ole.

concurrent-ruby-edge:

• (#1052) Fix dependency on concurrent-ruby to allow the latest release.

Release v1.3.1 (29 May 2024)

• Release 1.3.0 was broken when pushed to RubyGems. 1.3.1 is a packaging fix.

Release v1.3.0 (28 May 2024)

• (#1042) Align Java Executor Service behavior for shuttingdown?, shutdown?
• (#1038) Add Concurrent.available_processor_count that is cgroups aware.

... (truncated)

Commits

• 4c8fc28 Release 1.3.7
• d91ca94 Fix AtomicReference#update livelock when stored value is Float::NAN on JRuby ...
• 7e4d711 Fix ReentrantReadWriteLock read hold overflow into write-lock bit
• 6e37e06 Fix AtomicReference#update livelock when stored value is Float::NAN
• 2825cfa Cleanup spec
• 3fd4932 Fix ReadWriteLock wrong-thread write release and stray read release
• 1974b47 Add Ruby 4.0 in CI
• df8706d Add SECURITY.md (#1104)
• 7a1b789 Bump actions/upload-pages-artifact from 4 to 5
• 9b2dbf7 Bump actions/deploy-pages from 4 to 5
• Additional commits viewable in compare view

[paul]

There's currently some CVEs in concurrent-ruby 1.3.6:

$ ./bin/bundler-audit
Name: concurrent-ruby
Version: 1.3.6
CVE: CVE-2026-54904
GHSA: GHSA-h8w8-99g7-qmvj
Criticality: Unknown
URL: https://www.cve.org/CVERecord/SearchResults?query=CVE-2026-54904
Title: Concurrent Ruby - `AtomicReference#update` livelocks when the stored value is `Float::NAN`
Solution: update to '>= 1.3.7'

But I can't update it because of rails_error_dashboard:

$ bundle update concurrent-ruby rails_error_dashboard
Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Could not find compatible versions

Because rails_error_dashboard >= 0.1.28 depends on concurrent-ruby >= 1.3.0, < 1.3.7
  and Gemfile depends on rails_error_dashboard ~> 0.6,
  concurrent-ruby >= 1.3.0, < 1.3.7 is required.
So, because Gemfile depends on concurrent-ruby >= 1.3.7,
  version solving has failed.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.