Repository navigation
chore: release packages - #347
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
3ba5d4c to
0e8e034
Compare
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@unthrown/effect@6.0.0
Major Changes
7211584: Require Effect
^4.0.1and Node.js^20.19.0 || >=22.12.0, and migrate the interop bridgeto Effect 4. These Node releases enable the CommonJS entry to load Effect's ESM distribution.
Replace
toEither/fromEitherwithtoResult/fromResult, which useEffect's two-channel
Result(Success/Failure).toResultstill requiresan
onDefectcallback. The Exit and Effect bridge names and three-channelmapping are unchanged, including defect dominance in composite causes.
Applications staying on Effect 3 should keep
@unthrown/effect5.x.Summary by CodeRabbit
toEitherandfromEitherAPIs are replaced bytoResultandfromResult, usingSuccessandFailure.^4.0.1and Node.js^20.19.0or>=22.12.0. Applications using Effect 3 should remain on version 5.x.toResultstill requiresonDefect; Exit and Effect bridge names and three-channel cause mapping are unchanged.