Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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? Why?
ruby-3_0-bundle_auditfails because Ruby 3.0 resolves Active Support 7.1.6, which is affected by the following security advisories:The fixed Active Support release is 7.2.3.1 or later, but it requires Ruby 3.1 or later.
Updating the gemspec would drop Ruby 3.0 support, while ignoring the advisories would hide a real vulnerability. Since the other Ruby versions already run
bundle-audit, this removes only the non-actionable Ruby 3.0 audit job while keeping the Ruby 3.0 RuboCop, RSpec, and E2E jobs unchanged.How was it tested?
none