Completely forbid passing --ext to bundle gem without a value
#8976
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
martinemde
approved these changes
Sep 17, 2025
Contributor
martinemde
left a comment
There was a problem hiding this comment.
Nitpick test descriptions, otherwise good.
53cb375 to
9075c25
Compare
Co-authored-by: Martin Emde <[email protected]>
9075c25 to
9f34bf6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 was the end-user or developer problem that led to this PR?
When we added support for
rustextensions, we deprecated passing just--extand we now prefer specifying either--ext=cor--ext=rust.What is your fix for the problem, implemented in this PR?
Consolidate that breaking change.
Make sure the following tasks are checked