New version of concurrent-ruby (1.2.0) broke the build

[depfu]

We've tested your project with an updated dependency and the build failed.

This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.

name	version specification	new version
concurrent-ruby	~> 1.0	1.2.0

Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.

If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)

We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of concurrent-ruby for this test run.

What changed?

✳️ concurrent-ruby (~> 1.0 → 1.2.0) · Repo · Changelog

Release Notes

1.2.0

concurrent-ruby 1.2.0:

• (#975) Set the Ruby compatibility version at 2.3
• (#962) Fix ReentrantReadWriteLock to use the same granularity for locals as for Mutex it uses.
• (#983) Add FiberLocalVar
• (#934) concurrent-ruby now supports requiring individual classes (public classes listed in the docs), e.g., require 'concurrent/map'
• (#976) Let Promises.any_fulfilled_future take an Event
• Improve documentation of various classes
• (#972) Remove Rubinius-related code

concurrent-ruby-edge 0.7.0:

• (#975) Set the Ruby compatibility version at 2.3
• (#934) concurrent-ruby now supports requiring individual classes (public classes listed in the docs), e.g., require 'concurrent/map'
• (#972) Remove Rubinius-related code

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 63 commits:

• Fix rake release:test
• Adapt RakeCompilerDock to work with podman
• Seems plain `sh 'bundle package'` does not work
• Remove uptodate docs tasks
• 1.2.0
• More docs fixes
• Hide internal classes from public docs
• Update CHANGELOG
• Various fixes for ThreadLocalVar and FiberLocalVar
• Fix missing method `on_cruby?`.
• Add missing `require "concurrent/set.rb"`.
• Mark the `mutex_owned_per_thread?` method as private.
• Revert back to shared implementation of "locals" storage array.
• Introduce FiberLocalVar and LockLocalVar for alignment with `Mutex` scope.
• Don't compile the extension on non-CRuby, it's unused
• Review usages of defined?
• Ensure each file can be required separately
• Run each spec file in a process to detect missing requires
• Fix cycle between configuration and logging
• Some notes about setting up IntelliJ
• Update the list of maintainers
• Ensure the java extension is always loaded before it's needed
• The java extension is non-optional
• Simplify dependencies in concurrent/synchronization/volatile
• Rename to `@Lock` for consistency since it's a final ivar
• Be more explicit that it's only included once
• Extract safe initialization and use it for MutexAtomic{Reference,Fixnum,Boolean}
• Do not depend on Synchronization::LockableObject for MutexAtomicBoolean and MutexAtomicFixnum
• Fix circular dependency between AtomicReference and Synchronization::Object
• Concurrent.global_* should raise if there is an exception and not return nil
• Simplify Concurrent.monotonic_time to just use Process.clock_gettime(Process::CLOCK_MONOTONIC)
• MutexLockableObject/MonitorLockableObject never have any arguments
• Fix compiler warning (-Wold-style-definition)
• Cleanup old references to RbxAtomicReference
• rake clean should remove lib/concurrent-ruby/concurrent/concurrent_ruby_ext.so
• Skip flaky spec
• Add Ruby 3.2 to the CI matrix. Also update checkout action version
• Let `Promises.any_fulfilled_future` take an `Event`
• Update release docs instructions
• doc: typo
• ResolvableEvent#resolve(true) should raise on reassignment
• doc: Return type of Promises.any_event
• Add release date of v1.1.10 to CHANGELOG.md (#968)
• Fix #monotonic_get_time documentation typo
• Require Ruby 2.3+ and drop Ruby 2.2 support
• Update docs for Concurrent.processor_count
• Use TruffleRuby release in main CI
• Hide verbose and confusing "Pending: (Failures listed here ...)" section in RSpec output
• Fix warnings in extension
• Guard spec which correctly fails on 3.1
• Avoid raise_error without exception class
• Use lambda literals in Concurrent::Map spec
• Remove Rubinius-related code
• RUBY_ENGINE is always defined
• Fix documentation for Concurrent::Semaphore
• docs: use bundler cache
• Needs BUNDLE_WITH documentation
• Fix typo
• Automatically generate docs for master and last releases using GitHub Actions
• Remove docs from source repository
• Fix docs: Concurrent::Map#fetch_or_store is not atomic_method_with_block
• Update README.md
• Merge pull request #942 from ruby-concurrency/prep-release

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #666.