fix(templates): scope dependabot npm commits for the release policy - #19
Merged
Conversation
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.
Without
include: scope, Dependabot's root npm commits land asbuild: bump ...- no scope - so the pinned release policy[{"scope":"deps","type":"build","release":"patch"}]never matches and production dependency bumps silently never cut a patch release. Withinclude: scope, production bumps becomebuild(deps): ...(released as patch) and dev bumpsbuild(deps-dev): ...(correctly not released). PodNotes' hand-rolled config already had this; the shared template and the repos that copied it did not.Applied to the root npm entry only; a multi-directory setup like QuickAdd's
/docssite entry stays unscoped on purpose, since a docs-site dependency bump would otherwise also producebuild(deps):and release the plugin.