chore: silence deprecated version and unmet peer dependency warnings #1282
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.
Pre-flight Checklist
Please ensure you've completed all of the following.
Description of Change
pnpm.allowedDeprecatedVersions
pnpm.peerDependencyRules.allowedVersions
.npmrc
Motivation and Context
Warning logs for deprecated dependencies are popping up on every pnpm install and can be distracting for developers. Instead, now they are silenced and whenever specific dependencies are upgraded, it can be checked if entries from
pnpm.allowedDeprecatedVersions
can be removed. Pretty much the same is true for dependencies inpnpm.peerDependencyRules.allowedVersions
Screenshots
Before, unmet peer dependency warnings were ignored because they were throwing a warning instead of error only
After, no more peer dependency warnings and they would lead to exit code 1
Checklist
pnpm prepare-code
)pnpm test
passesRelease Notes