New: Treat Upgrade-tagged commits as patch releases#10
Open
taylortom wants to merge 1 commit into
Open
Conversation
The eslint preset's default release rules only trigger releases for Breaking, Fix, Update, and New tags. Upgrade-tagged commits — which are the natural fit for dep-range bumps — are silently dropped, even though Upgrade is in the project's documented tag list. Adding it as patch-level lets dep bumps surface as actual releases on consumer modules without requiring contributors to (mis)tag range-expansion commits as Fix.
taylortom
added
enhancement
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.
Adds
Upgradetocommit-analyzer.releaseRuleswithrelease: 'patch'.Patch is conservative — a dep bump usually doesn't change the module's API surface; if a particular Upgrade does warrant minor, contributors can use
Update:instead for that one commit.