Bump concurrent-ruby from 1.3.6 to 1.3.7

[dependabot]

Bumps concurrent-ruby from 1.3.6 to 1.3.7.

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.

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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[github-actions]

Test coverage

91.86% line coverage reported by SimpleCov.
Run: https://github.com/RaspberryPiFoundation/editor-api/actions/runs/28066182196

[cursor]

Stale comment

Dependabot assessment: concurrent-ruby 1.3.6 → 1.3.7

Verdict: Safe to merge. Lockfile-only patch bump; CI lint and full test suite both pass.

Verification

• CI: lint pass, test pass — 2507 examples, 0 failures (run).
• Local: Could not run tests here (no Docker; Ruby 4.0.5 install blocked by network/SSL). Relied on GitHub Actions.

Safety of merging

concurrent-ruby is transitive only (Rails/i18n/tzinfo, GoodJob, Flipper, Sentry). No direct Concurrent:: usage in application code. 1.3.7 is a security patch release (three low-severity CVEs in AtomicReference / lock primitives).

Residual risks unlikely to be exercised by the test suite:

• GoodJob worker threading — job executor pools use concurrent-ruby internally; production concurrency/race behaviour under sustained load is not fully simulated in CI.
• Boot-time singleton initialisation — Rails, i18n, and Flipper rely on concurrent-ruby thread-safety helpers; rare ordering/race issues at scale may not appear in the test environment.
• Patched CVE edge cases — the fixed bugs (Float::NAN in AtomicReference, reentrant read-lock overflow, manual ReadWriteLock release APIs) target APIs this app does not call directly; risk is limited to transitive gem internals.

Proposed fixes

None required — no test failures, no new Ruby/Rails deprecations attributable to this bump.

  

_{Sent by Cursor Automation: Editor-* - Tests Dependabot PRs}

[cursor]

Dependabot assessment: concurrent-ruby 1.3.6 → 1.3.7

Verdict: Safe to merge. Lockfile-only patch bump; CI lint and full RSpec suite passed on this branch.

Safety of merging

• Security-motivated patch — fixes three low-severity CVEs in AtomicReference, ReentrantReadWriteLock, and ReadWriteLock; updating is recommended.
• No direct app usage — concurrent-ruby is transitive only (via activesupport, i18n, tzinfo, flipper, good_job, sentry-ruby). No Concurrent:: references in application code.
• GoodJob thread pools — background job scheduling uses concurrent-ruby internally; edge cases around lock primitives are unlikely in normal operation but are not exercised by the test suite.
• Flipper feature flags — also depends on concurrent-ruby for in-process concurrency; same caveat as above for highly contended flag reads under extreme load.
• Sentry async transport — sentry-ruby uses concurrent-ruby for background event delivery; failure modes under thread-pool saturation are not typically covered by request specs.

Proposed fixes

None required — CI passed with no new deprecations or failures observed.

Verification

Check	Result
Lint (rubocop)	✅ pass
Tests (rspec)	✅ pass (3m 41s)
Local Docker run	⚠️ not available in this environment; relied on GitHub Actions

Assessed by Cursor automation.

  

_{Sent by Cursor Automation: Editor-* - Tests Dependabot PRs}