Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4.2: Limit concurrent-ruby to < 1.3.5 #6077

Merged
merged 1 commit into from
Jan 22, 2025

Conversation

mamhoff
Copy link
Contributor

@mamhoff mamhoff commented Jan 16, 2025

The concurrent-ruby gem drops a dependency on the logger gem, which
Rails 7.0 implicitly depends on. Rails 7.0 is out of bugfix maintenance,
so we won't see another release that has this bug fixed, so for Solidus
4.2 and 4.1 let's just limit concurrent-ruby to versions that do
depend on logger.

See rails/rails#54264

This approach has the advantage that we don't have to change the spec setup for every extension, because Solidus 4.2's dependencies take care of the problem.

@mamhoff mamhoff requested a review from a team as a code owner January 16, 2025 14:09
@github-actions github-actions bot added the changelog:repository Changes to the repository not within any gem label Jan 16, 2025
@mamhoff mamhoff force-pushed the v4-2-rails-branch branch 2 times, most recently from b34611e to 2bfd23e Compare January 16, 2025 16:47
@github-actions github-actions bot added changelog:solidus_core Changes to the solidus_core gem and removed changelog:repository Changes to the repository not within any gem labels Jan 16, 2025
@mamhoff mamhoff changed the title Use Rails branches instead of versions 4.2: Limit concurrent-ruby to < 1.3.5 Jan 16, 2025
@@ -35,6 +35,7 @@ Gem::Specification.new do |s|
s.add_dependency 'awesome_nested_set', '~> 3.3'
s.add_dependency 'cancancan', ['>= 2.2', '< 4.0']
s.add_dependency 'carmen', '~> 1.1.0'
s.add_dependency 'concurrent-ruby', '< 1.3.5'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a comment to the Rails issue?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added.

Copy link

codecov bot commented Jan 16, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.86%. Comparing base (8f41473) to head (62d5c3d).
Report is 2 commits behind head on v4.2.

Additional details and impacted files
@@           Coverage Diff           @@
##             v4.2    #6077   +/-   ##
=======================================
  Coverage   88.86%   88.86%           
=======================================
  Files         607      607           
  Lines       14752    14752           
=======================================
  Hits        13109    13109           
  Misses       1643     1643           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

The `concurrent-ruby` gem drops a dependency on the `logger` gem, which
Rails 7.0 implicitly depends on. Rails 7.0 is out of bugfix maintenance,
so we won't see another release that has this bug fixed, so for Solidus
4.2 and 4.1 let's just limit `concurrent-ruby` to versions that *do*
depend on `logger`.
Copy link
Contributor

@DanielePalombo DanielePalombo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️

@tvdeyen tvdeyen merged commit 289f693 into solidusio:v4.2 Jan 22, 2025
11 checks passed
@tvdeyen tvdeyen added the backport-v4.1 Backport this pull-request to v4.1 label Jan 22, 2025
Copy link

💚 All backports created successfully

Status Branch Result
v4.1

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-v4.1 Backport this pull-request to v4.1 changelog:solidus_core Changes to the solidus_core gem
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants