Fix Changesets 0.x to 1.0.0 escalation: drop workspace-internal peer deps#9
Merged
Merged
Conversation
…deps Convert @utaba/deep-memory (and @utaba/deep-memory-indexer in indexer-llm-anthropic) from peerDependencies to regular dependencies in the 5 workspace packages that re-exported it. Root cause: Changesets Decision 4 promotes a package to a major bump whenever a peer dependency's resolved range moves outside the existing range. Pre-1.0 caret semver only matches the same minor, so any minor bump of core escalated every package holding it as a peer to major. Major in any fixed-group member propagated to the entire group, producing 0.x to 1.0.0 jumps on every release cycle. Also: - Add @utaba/deep-memory-storage-neo4j to the fixed group in .changeset/config.json (the publishing guide already lists it as fixed; the config had drifted) - Update .changeset/anthropic-sdk-0-99-bump.md body to reflect the actual shipped delta (^0.98.0 to ^0.100.1, after dependabot #7 bumped the SDK further) - Correct the publishing-guide.md note explaining why the release GitHub Action was removed — the original explanation was wrong After this change, pnpm changeset status correctly plans the fixed group at 0.20.0 with no major bumps. Co-Authored-By: Claude Opus 4.7 (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
1 participant
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.
Root cause
pnpm changeset versionwas bumping the fixed group from0.19.0directly to1.0.0even though every pending changeset wasminororpatch. This is the same bug that originally forced removal of therelease.ymlGitHub Action.The trigger is Changesets Decision 4 (peer dependents major bump):
@utaba/deep-memoryas apeerDependencywithworkspace:^.minorbump oncoremoved its published range from^0.19.0to^0.20.0.1.0.0.Fix
Convert workspace-internal references from
peerDependencies→dependencies(workspace:^) in the five affected packages:embeddings-openaistorage-cosmosdbstorage-sqlserverstorage-neo4jindexer-llm-anthropicThe
fixedgroup in.changeset/config.jsonalready guarantees the version-lockstep invariant that peer deps were the wrong way to enforce.Also in this PR
@utaba/deep-memory-storage-neo4jto the fixed group in.changeset/config.json(the publishing guide listed it as fixed; config had drifted)..changeset/anthropic-sdk-0-99-bump.mdbody to reflect the actual shipped delta (^0.98.0→^0.100.1, after the dependabot bump).docs/publishing-guide.mdnote explaining whyrelease.ymlwas removed — the original explanation was wrong.Verification
Status now reports:
What is NOT changed
No consumer-facing API change. Consumers who already installed
@utaba/deep-memorydirectly see no behavioural difference; consumers who only installed a provider will now get core transitively (was previously a missing-peer-dep warning).