Work around missing logger dependency in Rails 6.1 and 7.0 #4298
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Downgrades concurrent-ruby to 1.3.4 to stop rails 6.1 from failing during bootstrap with the following error:
Motivation:
CI is red on master
Change log entry
None
Additional Notes:
Commit in concurrent-ruby removing logger dependency: ruby-concurrency/concurrent-ruby@d7ce956
Pointer to this being the issue: https://stackoverflow.com/questions/79360526/uninitialized-constant-activesupportloggerthreadsafelevellogger-nameerror
The issue affects Rails 6.1 and 7.0. 7.0 is fixed in rails/rails#54263. I take it 6.1 is not going to be fixed ever. When the next release after 7.0.8.7 comes out we should be able to remove the pin on concurrent-ruby from Rails 7.0 applications.
How to test the change?
Existing tests