Add --error-on-warn
to patch-package
#736
Merged
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 is the purpose of this PR?
patch-package
6.5.0 got a new CLI flag that we can find useful. With--error-on-war
added to inpostinstall
, CI in PRs like #734 will fail to flag a potential problem. Without the flag, we may merge Renovate PRs without noticing warnings like this:When the flag is added, the warning results exit code 1, so we'll always remember to update patches like in 4e68bce
🔗 Related links
Patches are not updated automatically, which would be possible to configure if we used self-hosted Renovate runners. I guess it's easier to just patch some packages manually for now.
🐾 Next steps
Check if
--error-on-war
works as expected in new PRs.🛡 What tests cover this?
❓ How to test this?
Check CI in newly created PRs (in the upcoming days)