Repository navigation
fix(effect-sdk): cap the effect peer below rc.118 - #1179
Merged
Merged
Maple Review Bot / Maple / review
succeeded
Sep 30, 2026 in 22s
Confidence 5/5 · No issues found
🟢 Confidence 5/5 · safe to merge
One-line peer bound plus its lockfile mirror; the range admits exactly the Effect pre-releases the SDK still supports.
quality 100/100 · no findings · tests not needed · risk low
Caps the @maple-dev/effect-sdk effect peer at >=4.0.0-rc.113 <4.0.0-rc.118 so rc.118 installs fail at resolve time instead of ERR_MODULE_NOT_FOUND at import, and mirrors it in bun.lock. Config-only, safe to merge.
effectpeer of@maple-dev/effect-sdknow bounded below4.0.0-rc.118bun.lockpeer entry updated to match
What was checked
- Peer range keeps the workspace on the cabal
effect4.0.0-rc.117, which satisfies both comparators (root package.json:92-100) - The two prerelease comparators make rc.113-rc.117 satisfy the range and rc.118 fail, so the bound does what the title claims
- All in-repo consumers of the SDK use
effect: catalog:effect, so no workspace package breaks on the tighter peer
38389dd · Updated on every push. Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.
Loading