declare DB-related environment variables for the Turbo test task so CI-provided DB settings reach Vitest
use Turbo env rather than passThroughEnv so DB config changes also invalidate the test cache
keep the repo's local fallback DB port unchanged at 5433, which still matches Docker Compose host mapping
Root Cause
Woodpecker sets DATABASE_URL for CI, but Turbo runs in strict environment mode. Without the DB variables declared on the test task, they never reach the Vitest process and the gateway tests fall back to the local default connection string.
Validation
pnpm format:check
pnpm typecheck
pnpm lint
Local test execution not run because this worktree does not have a Postgres service available
## Summary
- declare DB-related environment variables for the Turbo test task so CI-provided DB settings reach Vitest
- use Turbo env rather than passThroughEnv so DB config changes also invalidate the test cache
- keep the repo's local fallback DB port unchanged at 5433, which still matches Docker Compose host mapping
## Root Cause
Woodpecker sets DATABASE_URL for CI, but Turbo runs in strict environment mode. Without the DB variables declared on the test task, they never reach the Vitest process and the gateway tests fall back to the local default connection string.
## Validation
- pnpm format:check
- pnpm typecheck
- pnpm lint
- Local test execution not run because this worktree does not have a Postgres service available
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Root Cause
Woodpecker sets DATABASE_URL for CI, but Turbo runs in strict environment mode. Without the DB variables declared on the test task, they never reach the Vitest process and the gateway tests fall back to the local default connection string.
Validation