Remove patch-isolated bump type#22
Merged
Merged
Conversation
The concept added complexity for minimal benefit — in most monorepos using ^ ranges, a patch bump already stays in range without triggering propagation. Users who need to prevent propagation can use per-package dependencyBumpRules config instead. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Collaborator
|
The changes in this PR will be included in the next version bump.
|
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.
Summary
patch-isolatedbump type from types, core release plan logic, CLI, and all docsBumpTypeWithIsolatedtoBumpTypeWithNoneto reflect the remaining valid typesparseIsolatedBump()helper and allisolatedtracking in the release plan algorithmThe concept added complexity (threaded through Phase A/B/C) for minimal benefit — in most monorepos using
^ranges, a patch bump stays in range without triggering propagation. For cases where propagation prevention is needed, per-packagedependencyBumpRulesconfig is the right approach.Test plan
bumpy addinteractive flow works without isolated optionbumpy add --packages "pkg:patch"still works🤖 Generated with Claude Code