Repository navigation
Release 0.2.1: the CLI starts again and database stacks build - #3
Merged
Merged
Conversation
…with a database or auth
…stale v0.1 wording
0.2.0 crashed on start because @effect/platform-node's own range resolved @effect/platform-node-shared to 4.1.4. A bundled CLI resolves nothing on the user's machine. pnpm smoke:pack installs the packed tarball with npm in an empty directory and runs it; release.yml runs it before publishing.
…ll like npm create
drizzle-orm and effect-cf peer on @effect/sql-* with open ranges, so pnpm installed 4.1.4 drivers next to effect 4.0.5 and every database stack failed to build. The generated pnpm-workspace.yaml now overrides each family released with effect to the effect pin; add writes the overrides into older projects at their own effect version. Wildcard overrides need pnpm 12.17, so generated projects pin pnpm 12.21.0. The e2e harness checks the real lockfile and pnpm peers check after every install.
…ilter Vitest 5.1 joins describe and test names with " > ", so -t "stacks build <case>$" matches nothing and skips every case.
…it selects no test
effect and @effect/* 4.1.4, effect-cf 0.59.0, alchemy beta.87, better-auth 1.7.25, vite-plus 1.7.0, @effect/tsgo 0.70.0, oxlint 1.94.0, drizzle-orm and drizzle-kit to the official 1.0.0-rc.5, and the rest of bump.ts's list. vitest stays at 5.1.0, the copy vite-plus 1.7.0 bundles. vite-plus 1.7 runs type-aware lint on its bundled tsrs, so the tsgolint that effect-tsgo patches went unused and lint failed on an unknown effecttsgo rule. The lint and check scripts now run through effect-tsgo vp. bump.ts checks pins against tsgo's supported table and vite-plus's bundle. The browser extra's lockfile and image tag follow playwright 1.65.1.
alchemy 2.0.0-beta.87 moved the Cloudflare provider out of the alchemy package (alchemy/Cloudflare no longer exists) into @alchemy.run/cloudflare. The e2e peer check now fails on required or Effect peers only, and names the one upstream mismatch it tolerates (alchemy's runtime pulls unenv rc.25 next to @cloudflare/unenv-preset's exact rc.24 peer).
# Conflicts: # CONTRIBUTING.md # docs/limits.md # scripts/smoke-pack.ts
… add; release publishes the tarball it tested; CI runs the add e2e case
…lus's bundle) and prints why
… Effect overrides, scope the effect override to Effect 4, refresh an unedited dashboard so the realtime demo shows
…t checks git status and the warning, a test that --json --log-level=nope stays one JSON error
…ime; fixture README names the project
amagdy46
marked this pull request as ready for review
November 18, 2026 17:42
Codex Review Summary: ✅ CompletedThis 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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
npm create efforgecrashes on startup today, and most generated projects failpnpm build. This fixes both, fixes the other bugs a new user hit, and adds the CI guards that would have caught it.What was broken
pnpm dlx. 0.2.0 pinned@effect/platform-node@4.0.5, which depends on@effect/platform-node-shared: ^4.0.5. That range now resolves to 4.1.4, which needs Effect 4.1.pnpm build. drizzle-orm and effect-cf pulled Effect 4.1 SQL packages in next to Effect 4.0.5.>, so the-tfilter matched nothing and every e2e job passed with 17 tests skipped. CI also had no scheduled run.addleft apnpm-lock.yamlbehind and then warned about it;addgenerated a route tree on a never-installed project; a mistyped flag printed 49 lines of help, also under--json; docs and errors still said "v0.1".What changed
--helpwent from 682 ms to 265 ms.overridesinpnpm-workspace.yaml, and pin pnpm 12.21.0 (ADR 0005). Libraries that depend on Effect 3 keep their own copy.addrepairs projects created by 0.2.0: it writes the overrides and raisespackageManagerwhen the project's pnpm is too old to honour them. The changelog has the manual repair.@effect/tsgo0.70.0, Alchemy beta.87 (provider moved to@alchemy.run/cloudflare), the official Drizzle1.0.0-rc.5. Vitest stays at 5.1.0 on purpose, to match the copy Vite+ bundles.adde2e case.release.ymlpacks once, smoke-tests that tarball and publishes the same file, still with trusted publishing and provenance.How it was verified
Locally, at the head commit:
pnpm smoke:pack: the tarball installed with npm in an empty directory with no lockfile, run through npm, npx andpnpm dlx; creates the default stack, builds it, adds email, builds again.addcase pass. The browser flow passes against Postgres 17.add emailwith this branch:pnpm buildpasses andpnpm peers checkis clean.v0.2.0tag: all addressed.On GitHub: this pull request's CI is the first time the e2e matrix has really run. Its first run passed 20 of 21 jobs and caught one more real bug: with
CIset, pnpm freezes the lockfile, so the install afterefforge addfailed withERR_PNPM_OUTDATED_LOCKFILE.addnow installs with--no-frozen-lockfile, and all 21 checks pass.Still only provable after merge: the daily schedule, and publishing through the changed release workflow.
To release
main.git tag v0.2.1 && git push origin v0.2.1.release.ymlsmoke-tests the tarball and publishes it.