ci(bump): gracefully handle no bump-eligible commits#1950
Merged
bearomorphism merged 1 commit intomasterfrom May 8, 2026
Merged
ci(bump): gracefully handle no bump-eligible commits#1950bearomorphism merged 1 commit intomasterfrom
bearomorphism merged 1 commit intomasterfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1950 +/- ##
=======================================
Coverage 98.23% 98.23%
=======================================
Files 61 61
Lines 2772 2772
=======================================
Hits 2723 2723
Misses 49 49 ☔ View full report in Codecov by Sentry. |
bearomorphism
force-pushed
the
ci/fix-bumpversion-no-commits
branch
from
ca48e4b to
1f395a7
Compare
When commits like docs:, ci:, or build(deps): are pushed to master, cz bump exits with code 21 (NO_COMMITS_TO_BUMP), failing the workflow. Handle exit code 21 explicitly by setting bumped=false and exiting 0. Subsequent changelog and release steps are now conditional on bumped == 'true', so they are skipped when there is nothing to release. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
bearomorphism
force-pushed
the
ci/fix-bumpversion-no-commits
branch
from
1f395a7 to
e483556
Compare
Lee-W
approved these changes
May 8, 2026
Member
|
sweet! |
Member
This was referenced May 8, 2026
Collaborator
Author
This was referenced May 9, 2026
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
3 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.
Description
When non-bump-eligible commits (e.g.
docs:,ci:,build(deps):) are pushed to master,cz bump --yesexits with code 21 (NO_COMMITS_TO_BUMP), causing the bump workflow to fail.Out of the last 20 runs, ~12 failed this way — see recent example.
This PR handles exit code 21 explicitly: log a message, set
bumped=false, and exit 0. TheBuild changelogandReleasesteps are now conditional onbumped == 'true'. All other non-zero exit codes still fail the workflow as before.Checklist
Was generative AI tooling used to co-author this PR?
Generated-by: GitHub Copilot following the guidelines
Code Changes
Documentation Changes
N/A — CI workflow only.
Expected Behavior
When commits like
docs:,ci:, orbuild(deps):are pushed to master, the bump workflow should succeed gracefully (with a "No bump-eligible commits found" message) instead of failing with exit code 21.Steps to Test This Pull Request
docs:orci:commit to masterAdditional Context
Related workflow:
.github/workflows/bumpversion.yml