Repository navigation
chore: update Effect to 4.0 RC - #12
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b0794be496
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "@phosphor-icons/core": "2.1.1", | ||
| "@sinclair/typebox": "0.34.52", | ||
| "effect": "4.0.0-beta.97", | ||
| "effect": "4.0.0-rc.108", |
There was a problem hiding this comment.
Keep Effect aligned with Foldkit's exact peers
With foldkit and @foldkit/ui still pinned to 0.131.0, their lock entries require exactly Effect/platform-browser 4.0.0-beta.97; upgrading the app alone to rc.108 leaves an unsupported peer graph and installs a second beta platform-browser under Foldkit (bun.lock lines 1038 and 1520). The app passes RC-created effects directly into Foldkit's Command.define callbacks, so this can produce incompatible command values or runtime API failures; upgrade Foldkit to an RC-compatible release or retain its required Effect versions.
AGENTS.md reference: AGENTS.md:L55-L56
Useful? React with 👍 / 👎.
Updates Effect and platform packages to 4.0.0-rc.108 and regenerates the Bun lockfile. Aligns the four stale source/study workspace manifests to the same RC, removing duplicate SchemaAST and Constraint identities across package boundaries.\n\nVerification: bun run check passed: formatting, Oxlint, i18n validation, and every repository TypeScript configuration.