Repository navigation
ci: give Dependabot pull requests conventional titles - #43
Merged
Merged
Conversation
kurkle
force-pushed
the
ci/dependabot-conventional-titles
branch
2 times, most recently
from
November 19, 2026 17:59
8b73c47 to
2448218
Compare
Add a dependabot.yml that only sets a chore commit-message prefix with scope (chore(deps) / chore(deps-dev)) so Dependabot pull request titles pass the semantic title check without publishing a release. Version updates stay disabled via open-pull-requests-limit: 0.
kurkle
force-pushed
the
ci/dependabot-conventional-titles
branch
from
November 19, 2026 18:02
2448218 to
d4b943b
Compare
|
🎉 This PR is included in version 1.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
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.
Problem
The repository merges only by squash, and the squash commit takes the pull request title, which semantic-release reads.
pr-title.ymltherefore validates every title as a conventional commit.There is no
.github/dependabot.yml, so Dependabot titles its pull requests with its default "Bump x from a to b". These fail the title check (for example #41, wheretestpasses andlintfails) and would not be meaningful release triggers anyway.Change
Adds a
.github/dependabot.ymlwith a singlenpmentry whose only purpose iscommit-message, which Dependabot uses for both commit messages and pull request titles:prefix: chore+include: scopegiveschore(deps): bump x from a to bfor the runtime dependency (pixelmatch) andchore(deps-dev): bump x from a to bfor devDependencies.include: scopeappendsdeps/deps-devto the prefix, so the prefix is the bare type.choredoes not release, so Dependabot pull requests do not publish on their own. Onlypackage.jsonreaches consumers and the lockfile is not published, so a lockfile-only bump (including a runtime dependency moving within its existing range, and any transitive package) leaves the published package unchanged and needs no release. When a bump changes a runtime dependency's range inpackage.json(currently onlypixelmatch), edit the pull request title tofix(deps): ...before merging so that it publishes a patch.What does not change
Which pull requests Dependabot opens.
open-pull-requests-limit: 0keeps version updates disabled, as they are today. GitHub documents this setting as the way to receive only security updates ("you can setopen-pull-requests-limitto0in order to prevent version updates for a givenpackage-ecosystem"), and security update pull requests follow the entry'scommit-messagesettings.schedule.intervalis a required key, soweeklyis set; with the limit at 0 it has no effect.Limits