New version of concurrent-ruby (1.3.4) 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.3.4

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.3.4) · Repo · Changelog

Release Notes

1.3.4

What's Changed

• Update comment for JRuby variant of processor_count to reality by @meineerde in #1054
• Add Concurrent.cpu_requests that is cgroups aware. by @heka1024 in #1058
• Fix the doc of Concurrent.available_processor_count by @y-yagi in #1059
• Fix the return value of Concurrent.available_processor_count when cpu.cfs_quota_us is -1 by @y-yagi in #1060

New Contributors

• @heka1024 made their first contribution in #1058
• @y-yagi made their first contribution in #1059

Full Changelog: v1.3.3...v1.3.4

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

Commits

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

• Avoid requiring files of the gem in Rakefile to avoid redefined method warnings
• Avoid require in Gemfile & Rakefile to avoid redefined constant warnings
• Avoid require in *.gemspec files to avoid redefined constant warnings
• Update docs-source/signpost.md
• 1.3.4
• Check early that $CONCURRENT_JRUBY_HOME is set
• Fix the return value of `Concurrent.available_processor_count` when `cpu.cfs_quota_us` is -1
• Fix the doc of `Concurrent.available_processor_count`
• Add `Concurrent.cpu_shares` that is cgroups aware.
• Update comment for JRuby variant of processor_count to reality