v0.0.8
Local automation and Playwright E2E release for the Next.js application template.
v0.0.8
v0.0.8 adds local automation auth and Playwright E2E infrastructure. The release makes browser automation practical for local development while keeping the automation flow explicitly disabled in production.
Highlights
- Added opt-in local automation auth for Playwright, browser-use, and agent-driven browser checks.
- Added
/api/local-auth/scenariofor creating signed-in automation users and cleaning them up. - Added a gated login-page automation panel for local test-user creation.
- Added Playwright scripts, configuration, Chromium smoke coverage, reports, traces, screenshots, and videos.
- Added route warming and first-party error detection helpers for E2E runs.
- Added Better Auth organization hooks that enforce workspace domain and team invitation policy.
What changed for template users
Local automation users use the local-agent+...@local-agent.test namespace and are only available
when LOCAL_AUTOMATION_AUTH_ENABLED=true outside production. The scenario route creates a real
Better Auth session cookie, so browser tests exercise the same protected pages as a signed-in user.
Playwright now has a default local workflow: install Chromium once, run npm run e2e, and let the
suite start the development server with the expected automation environment.
Upgrade notes
- No Prisma migration is required for this release.
- Never enable
LOCAL_AUTOMATION_AUTH_ENABLEDin production. - Run
npm run e2e:installonce on machines that need the Playwright browser. npm run e2estarts a development server unlessPLAYWRIGHT_START_SERVER=false.- The default Playwright base URL is
http://127.0.0.1:3127. - Playwright artifacts are ignored under
playwright-report,test-results/playwright, andblob-report.
Quality
The release adds tests for local automation gating, credential generation, scenario create/cleanup, login panel behavior, organization invitation policy hooks, route config behavior, and a public UI smoke test for the home-to-login flow.