Skip to content

fix(browser-tests): run the CI suite in development mode - #87

Merged
VladUZH merged 1 commit into
mainfrom
fix/browser-ci-dev-env
Jul 29, 2026
Merged

fix(browser-tests): run the CI suite in development mode#87
VladUZH merged 1 commit into
mainfrom
fix/browser-ci-dev-env

Conversation

@VladUZH

@VladUZH VladUZH commented Jul 29, 2026

Copy link
Copy Markdown
Member

Second validation dispatch (run 30450267639) failed with 8× Create agent failed: 403 plus a 34-timeout cascade. Root cause: the job had no NODE_ENV, so the API enforced API-key auth in CI while locally apps/api/.env sets development mode (documented dev auth bypass). The seeded key is deliberately runtime-only (no agents:write) — the suite's test-data helper hit the same scope wall real signups used to.

The suite is a dev-mode harness by design (dev servers, seeded DB, dev login); NODE_ENV: development makes CI match the environment the suite was written for.

Will re-dispatch after merge for a third validation run.

🤖 Generated with Claude Code

The suite is a dev-mode E2E harness: locally apps/api/.env sets
NODE_ENV=development and the API's documented dev auth bypass applies.
The CI job had no NODE_ENV, so the API enforced API-key auth and the
seeded runtime-only key (deliberately without agents:write) 403'd every
test-data agent creation, cascading into 34 selector timeouts.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@VladUZH
VladUZH merged commit 1806121 into main Jul 29, 2026
19 checks passed
@VladUZH
VladUZH deleted the fix/browser-ci-dev-env branch July 29, 2026 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant