Repository navigation
fix(templates): update Effect to 4.0.6 for Alchemy infra - #1297
Conversation
@alchemy.run/frontend-frameworks depends on @effect/platform-node ^4.0.0, which now resolves to 4.0.6 and brings effect 4.0.6. With effect and the platform packages pinned to 4.0.5, generated infra packages ended up with two copies of effect and alchemy.run.ts failed to typecheck.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
WalkthroughThe template generator updates the pinned versions of ChangesTemplate dependency update
Priority: ➖ Normal Merge Risk: ⚪ Minimal · up to
|
Summary
Generated Alchemy infra packages (Prisma Compute, Cloudflare, Axiom) pin
effect,@effect/platform-nodeand@effect/platform-bunto4.0.5.@alchemy.run/frontend-frameworks@2.0.0-beta.83depends on@effect/platform-node ^4.0.0, which resolves to 4.0.6 since 2026-10-22 and bringseffect4.0.6. The project then has two copies ofeffect, andalchemy.run.tsfailscheck-types:This moves all three pins to 4.0.6, the latest release. The failure shows up on main and on every open PR's
prisma-react-router-web-npmsample (see #1295).Verification
bun run checkBTS_BUILD_SAMPLE_FILTER=prisma-react-router-web-npmgenerated build: failed before, passes nowSummary by CodeRabbit