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.
Description
@commitlint/config-lerna-scopes
works fine with the latest versions of lerna. Thanks to the production dependency it doesn't actually need a peer version of lerna at runtime. But we do need to be sure that using@lerna/project@6
continues to work with the latest lerna setup. I can confirm that it does, and this PR just formalizes compatibility.Motivation and Context
Declaring compatibility removes peer dependency noise from package managers like yarn and pnpm when using this shared config with the latest versions of lerna.
Usage examples
# Should produce no warnings pnpm add -D lerna @commitlint/config-lerna-scopes
How Has This Been Tested?
We've been tolerating the peer dependency warning and using this shared config together with lerna v7 and v8 across dozens of repos without issue for over a year.
Types of changes
Calling this a feature since it technically adds formal support.
Checklist: