Repository navigation
Refactor version propagation into Phase A/B/C architecture - #14
Merged
Merged
Conversation
Restructure the release plan algorithm into three distinct phases: - Phase A: always fix out-of-range deps (peer deps get "match" bump, regular deps get patch, devDeps skipped) - Phase B: enforce fixed/linked group constraints - Phase C: opt-in proactive propagation via dependencyBumpRules and cascadeTo Key changes: - Peer dep out-of-range bumps now match the triggering bump level (not hardcoded major) - workspace:^ and workspace:~ resolved to ^/~<currentVersion> for range checking - Remove minor-isolated (only patch-isolated remains), add 'none' to suppress propagated bumps - Remove specificDependencyRules (use per-package dependencyBumpRules instead) - DEFAULT_BUMP_RULES: devDependencies is now false, peerDependencies uses bumpAs: "match" - DependencyBumpRule.trigger no longer accepts 'none'; use false for the whole rule - updateInternalDependencies loses 'none' option - Remove getCaretZeroPeerDepWarnings; warnings now emitted inline during Phase A - Add plan.warnings array to ReleasePlan for ^0.x propagation warnings - patch-isolated and none throw errors when they would leave broken ranges Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The changes in this PR will be included in the next version bump.
|
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
workspace:^/~to real semver ranges before checking.dependencyBumpRulesandcascadeTo. Only active whenupdateInternalDependenciesis"patch"or"minor".Breaking changes to config
minor-isolatedbump type (usepatch-isolatedinstead)specificDependencyRules(usecascadeToon the source package instead)updateInternalDependencies: "none"(use"out-of-range"instead)DependencyBumpRuleno longer acceptstrigger: "none"— set the whole rule tofalseinsteadpeerDependenciesrule changed from{ trigger: "major", bumpAs: "major" }to{ trigger: "major", bumpAs: "match" }devDependenciesrule changed from{ trigger: "none", bumpAs: "patch" }tofalseNew features
nonebump type in changesets to suppress propagated bumps (validated against broken ranges)patch-isolatednow errors if it would leave broken ranges (instead of silently skipping)workspace:^/~resolved to real semver ranges for propagation checks^0.xpeer dep propagation andworkspace:*on peer depsdocs/version-propagation.mdexplaining the full algorithmTest plan
bun test)workspace:^resolved correctly,^0.xgenerates warningspatch-isolatederrors on broken ranges, skips Phase C when ranges satisfiednonesuppresses bumps, errors on broken ranges🤖 Generated with Claude Code