CodeCow/stack
1
0
Fork 0
mirror of https://github.com/stack-auth/stack.git synced 2026-06-30 21:01:54 +08:00
Code Issues Actions 44 Packages Projects Releases Wiki Activity

Fix local-emulator e2e: use canonical HEXCLAVE_ var to avoid dual-read conflict

Browse Source 
The dashboard build inlines both NEXT_PUBLIC_HEXCLAVE_* and NEXT_PUBLIC_STACK_*
spellings and throws when they're set to different non-empty values. The job set
the legacy NEXT_PUBLIC_STACK_IS_LOCAL_EMULATOR=true while the dashboard commits
NEXT_PUBLIC_HEXCLAVE_IS_LOCAL_EMULATOR=false in .env.development, so every build
crashed on the conflict check.

Set the canonical NEXT_PUBLIC_HEXCLAVE_IS_LOCAL_EMULATOR=true instead: the
job-level value overrides the committed default (process.env wins over dotenv)
and leaves no conflicting STACK_ twin.
This commit is contained in:
Bilal Godil 2026-06-16 18:12:36 -07:00
parent 1ede37281f
commit e78ec78471
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
.github/workflows/e2e-api-tests-local-emulator.yaml vendored
View File

@ -17,7 +17,12 @@ jobs:
runs-on: ubicloud-standard-8
env:
NODE_ENV: test
NEXT_PUBLIC_STACK_IS_LOCAL_EMULATOR: "true"
# Use the canonical HEXCLAVE_ name: the dashboard commits a differing
# NEXT_PUBLIC_HEXCLAVE_IS_LOCAL_EMULATOR=false in .env.development, and the
# dual-read conflict check throws if both spellings are set to different
# values. Setting the canonical name here overrides that committed default
# (process.env wins over dotenv) without leaving a conflicting STACK_ twin.
NEXT_PUBLIC_HEXCLAVE_IS_LOCAL_EMULATOR: "true"
STACK_ENABLE_HARDCODED_PASSKEY_CHALLENGE_FOR_TESTING: yes
STACK_DATABASE_CONNECTION_STRING: "postgres://postgres:PASSWORD-PLACEHOLDER--uqfEC1hmmv@localhost:8128/stackframe"
STACK_EXTERNAL_DB_SYNC_MAX_DURATION_MS: "20000"