Skip to content

fix(deps): widen @mind-studio/ui peer to >=0.3.0 → core 0.7.1 - #11

Merged
rep0x merged 1 commit into
mainfrom
fix/core-ui-peer-range
Jun 20, 2026
Merged

fix(deps): widen @mind-studio/ui peer to >=0.3.0 → core 0.7.1#11
rep0x merged 1 commit into
mainfrom
fix/core-ui-peer-range

Conversation

@rep0x

@rep0x rep0x commented Jun 20, 2026

Copy link
Copy Markdown
Member

Problem

core 0.7.0 declares peerDependencies["@mind-studio/ui"] = "^0.3.0". For a 0.x range, ^0.3.0 = >=0.3.0 <0.4.0, so it excludes the published ui 0.4.0 the fleet uses. Consumers installing ui ^0.4.0 + core ^0.7.0 hit ERESOLVE (peer conflict) under npm ci.

Fix

Widen the optional peer to >=0.3.0 — a true floor that admits 0.3.x and every later 0.x. Ships as core 0.7.1; ^0.7.0 consumer pins pick it up automatically.

Unblocks the Wave 2 consumer PRs (ui#20).

^0.3.0 resolves to >=0.3.0 <0.4.0 for a 0.x range, which excludes the
published ui 0.4.0 the fleet now uses and triggers an ERESOLVE peer
conflict in consumers. Widen to a true floor so core 0.7.x is compatible
with ui 0.3.0 and every later 0.x.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@rep0x
rep0x merged commit 1d8b181 into main Jun 20, 2026
1 check passed
@rep0x
rep0x deleted the fix/core-ui-peer-range branch June 20, 2026 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant