Repository navigation
Rework check commands: --strict and --no-fail flags - #37
Merged
Merged
Conversation
Collaborator
|
The changes in this PR will be included in the next version bump.
|
theoephraim
force-pushed
the
fix/empty-bump-file-detection
branch
from
April 22, 2026 04:28
dd2c7fd to
fa1ea46
Compare
- Default: only fail when no bump files exist at all (matches changesets) - --strict: fail if any changed package is uncovered - --no-fail: advisory-only, never exit non-zero - Fix false positive empty bump file detection from deleted files - Use log.error when failing, log.warn when not - Update docs for new flags, none bump type, and removed --fail-on-missing Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
theoephraim
force-pushed
the
fix/empty-bump-file-detection
branch
from
April 22, 2026 04:35
fa1ea46 to
d5771b2
Compare
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
--strictflag for bothbumpy checkandbumpy ci check— fails if any changed package is not covered by a bump file--no-failflag — advisory-only mode, never exits non-zerolog.error(stderr) when failing,log.warn(stdout) when not--fail-on-missingfromci check(superseded by new flags)nonebump type in strict mode,--emptyin default modeTest plan
bumpy checkwarns about uncovered packages but exits 0 (default)bumpy check --strictwould exit 1 for uncovered packages🤖 Generated with Claude Code