chore(ci): scope dependabot prefixes so release-please skips non-runtime updates#48
Merged
Merged
Conversation
…ime updates Runtime deps -> fix(deps) (patch bump). Dev deps -> chore(deps-dev) (no bump). GH Actions / reusable workflows -> chore(ci) (no bump). Verified on openCoreEMR/release-please-test that release-please honors these prefixes: only fix(deps) lands in the next release PR; chore(deps-dev) and chore(ci) are excluded from version bumping.
msummers42
approved these changes
May 18, 2026
msummers42
left a comment
There was a problem hiding this comment.
Approved as bulk process of identical changesets
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.
Summary
Scope Dependabot's commit-message prefixes so release-please only opens a release PR when something user-facing actually changed.
depsfix(deps)deps-devchore(deps-dev)depschore(ci)Why
Today every Dependabot PR lands as
deps:ordeps-dev:, both of which release-please's default conventionalcommits config treats as version-bumping. The fleet symptom: release PRs whose only payload is a dev-only bump (rector, phpunit, composer-normalize) or a reusable-workflow update — noise releases that ship nothing user-facing.Verified
Tested on openCoreEMR/release-please-test:
fix(deps):→ added under Bug Fixes in the next release PR (patch bump)chore(deps-dev):→ absent from release PR (no bump)chore(ci):→ absent from release PR (no bump)Test plan
fix(deps)/chore(deps-dev)/chore(ci)prefixes.chore(...)-only changes.