ci: release on dependency bumps via deps: prefix - #83
Merged
Merged
Conversation
release-please only bumps versions for feat/fix/breaking by default, so the recent run of chore(deps) dependency bumps landed on main without cutting a release. - release-please-config.json: add changelog-sections. feat/fix/perf/ deps/revert are visible and release-triggering; chore/ci/build/docs/ style/refactor/test are explicitly hidden and non-releasing. A type listed here without "hidden": true is treated as release-triggering by release-please, so deps: now bumps a patch. - .github/renovate.json: semanticCommitType "deps" (scope dropped) so dependency PRs merge as "deps: ...", landing in a dedicated Dependencies changelog section and cutting a patch release. The github-actions manager is carved out to chore: since action digest pins don't change the bundled extension. - CLAUDE.md: document the commit-prefix conventions.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
2 participants
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
release-pleaseonly bumps versions forfeat:/fix:/ breaking changes by default. The recent run ofchore(deps)dependency bumps therefore landed onmainwithout cutting a release.Changes
release-please-config.json— addchangelog-sections.feat/fix/perf/deps/revertare visible and release-triggering;chore/ci/build/docs/style/refactor/testare explicitly"hidden": trueand non-releasing. A commit type listed here without"hidden": trueis treated as release-triggering by release-please (googleapis/release-please#2638), sodeps:now bumps a patch and files under a dedicated Dependencies changelog section..github/renovate.json—semanticCommitType: "deps"with the scope dropped, so dependency PRs merge asdeps: update foo to 1.2.3. Thegithub-actionsmanager is carved out tochore:since action digest pins don't change the bundled extension.CLAUDE.md— document the commit-prefix conventions.Net effect
Any Renovate dependency PR now cuts a patch release. GitHub Actions bumps and
ci:/chore:commits still don't. The dev→main promotion is a merge commit (not squash), so individualdeps:commits stay visible to release-please.Targeting
mainOpened against
mainrather thandevelopmentbecauserelease-please-config.jsonis only consumed by the release-please action, which runs onmain— same rationale as the CI-fix exception.propagate-main-to-development.ymlcarries it back down.