fix(pi-simplify): widen peer ranges to allow 0.75.x#127
Merged
MattDevy merged 1 commit intoMay 24, 2026
Conversation
Bump @earendil-works/pi-ai, pi-coding-agent, and pi-tui peer ranges from ^0.74.0 to >=0.74.0 <0.76.0 in packages/pi-simplify/package.json. The 0.74-only ceiling blocks any consumer that installs another extension peering ^0.75.x (e.g. pi-rtk-optimizer@0.8.0) alongside pi-simplify, breaking 'pi update' with ERESOLVE. The 0.74 -> 0.75 upgrade is API-compatible for the surface area used here, so the range can be widened without code changes.
MattDevy
approved these changes
May 24, 2026
Owner
MattDevy
left a comment
MattDevy
left a comment
There was a problem hiding this comment.
LGTM! Thank you for raising a PR to fix this 😀
MattDevy
changed the title
Merged
MattDevy
added a commit
that referenced
this pull request
May 24, 2026
🤖 I have created a release *beep* *boop* --- <details><summary>pi-simplify: 0.2.2</summary> ## [0.2.2](pi-simplify-v0.2.1...pi-simplify-v0.2.2) (2026-05-24) ### Bug Fixes * **pi-simplify:** Widen peer ranges to allow 0.75.x ([#127](#127)) ([de2757a](de2757a)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
2 tasks
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
Widen the
@earendil-works/pi-{ai,coding-agent,tui}peer ranges inpackages/pi-simplify/package.jsonfrom^0.74.0to>=0.74.0 <0.76.0.The current
^0.74.0ceiling (<0.75.0) prevents installing any extension that peers^0.75.x(e.g.pi-rtk-optimizer@0.8.0) alongsidepi-simplify. npm resolves the intersection to0.74.xfor pi-simplify's constraint, then the newer extension's^0.75.4peer is unsatisfiable, andpi updatefails withERESOLVE.Pi runtime itself shipped 0.75 weeks ago and
pi -valready reports0.75.xon current installs, so widening the range realigns the peer with the runtime already deployed.Widening to
>=0.74.0 <0.76.0(caret-OR equivalent:^0.74.0 || ^0.75.0) keeps existing 0.74.x users working while unblocking the 0.75 line.Note: this is the same kind of fix being requested over at nicobailon/pi-powerline-footer#67 — pi-simplify hits the exact same downstream conflict.
Scoped to
pi-simplifyonly; happy to do the equivalent change across the other packages in this monorepo if you want — just say the word and I'll send follow-up PRs.Test plan
pi install npm:pi-rtk-optimizeron a host that already haspi-simplifyinstalled — should resolve cleanly without--legacy-peer-depspi updateshould succeed on a host with the current extension set