Skip to content

ci: give Dependabot pull requests conventional titles - #43

Merged
kurkle merged 1 commit into
chartjs:masterfrom
kurkle:ci/dependabot-conventional-titles
Nov 19, 2026
Merged

kurkle merged 1 commit into
chartjs:masterfrom
kurkle:ci/dependabot-conventional-titles

Conversation

@kurkle

@kurkle kurkle commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

Problem

The repository merges only by squash, and the squash commit takes the pull request title, which semantic-release reads. pr-title.yml therefore 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, where test passes and lint fails) and would not be meaningful release triggers anyway.

Change

Adds a .github/dependabot.yml with a single npm entry whose only purpose is commit-message, which Dependabot uses for both commit messages and pull request titles:

  • prefix: chore + include: scope gives chore(deps): bump x from a to b for the runtime dependency (pixelmatch) and chore(deps-dev): bump x from a to b for devDependencies. include: scope appends deps / deps-dev to the prefix, so the prefix is the bare type.

chore does not release, so Dependabot pull requests do not publish on their own. Only package.json reaches 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 in package.json (currently only pixelmatch), edit the pull request title to fix(deps): ... before merging so that it publishes a patch.

What does not change

Which pull requests Dependabot opens. open-pull-requests-limit: 0 keeps version updates disabled, as they are today. GitHub documents this setting as the way to receive only security updates ("you can set open-pull-requests-limit to 0 in order to prevent version updates for a given package-ecosystem"), and security update pull requests follow the entry's commit-message settings. schedule.interval is a required key, so weekly is set; with the limit at 0 it has no effect.

Limits

  • Existing open Dependabot pull requests (such as Bump @vitest/browser from 5.0.0 to 5.0.5 #41) keep their old title until Dependabot recreates or rebases them.
  • This cannot be exercised before merge. The effect can only be observed on the next Dependabot pull request after this is merged.

@kurkle
kurkle force-pushed the ci/dependabot-conventional-titles branch 2 times, most recently from 8b73c47 to 2448218 Compare November 19, 2026 17:59
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
kurkle force-pushed the ci/dependabot-conventional-titles branch from 2448218 to d4b943b Compare November 19, 2026 18:02
@kurkle
kurkle merged commit ee1102e into chartjs:master Nov 19, 2026
3 checks passed
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 1.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant