fix(effect-sdk): cap the effect peer below rc.118 - #1179
Conversation
rc.118 removed the effect/unstable/{http,observability} paths the SDK imports,
so the open-ended range let installs succeed and then fail at runtime. The
monorepo stays on rc.117 until alchemy and effect-clickhouse support rc.118.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 2 minutes. View limit detailsLimit details: You’ve used all 4 included reviews currently available. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Maple review🟢 Confidence 5/5 · safe to merge Caps the
What was checked
|
Effect
4.0.0-rc.118removed theeffect/unstable/{http,observability}paths the SDK imports. The open-ended peer (>=4.0.0-rc.113) let installs succeed and then fail withERR_MODULE_NOT_FOUNDat import.effect→>=4.0.0-rc.113 <4.0.0-rc.118, so package managers flag rc.118 at install timebun.lockupdated for the peer changeThe SDK stays on the same Effect version as the monorepo, which can't move to rc.118 until alchemy (beta.79) and
@maple-dev/effect-clickhousestop importingeffect/unstable/*. Supersedes #1175.After merge: publish 0.9.0. The published 0.8.2 calls
Config.string/Config.redacted, which no longer exist from rc.113 on, so no working release is on npm today.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.