Add a --warn-error flag - #1718
Merged
Merged
Conversation
Test Results 17 files 38 suites 0s ⏱️ Results for commit ad07af7. ♻️ This comment has been updated with latest results. |
Alasdair
force-pushed
the
warn_error
branch
2 times, most recently
from
July 30, 2026 15:55
9eb6337 to
ca7dabf
Compare
This flag promotes warnings to errors. It only works in conjunction with the `--required-version` flag. Each warning now--and going forwards, has a specified version where it was introduced (all current warnings are marked as 0.20.2). Any warning with an introduced version less than or equal to the required version will become an error. This means that new warnings can be introduced without breaking downstream CI builds that want to use the flag.
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.
This flag promotes warnings to errors. It only works in conjunction with the
--required-versionflag. Each warning now and going forwards, has a specified version where it was introduced (all current warnings are marked as 0.20.2). Any warning with an introduced version less than or equal to the required version will become an error. This means that new warnings can be introduced without breaking downstream CI builds that want to use the flag.