mirror of
https://github.com/stack-auth/stack.git
synced 2026-06-30 21:01:54 +08:00
b270c0f2ef
Addresses correctness/coverage issues found reviewing the STACK_*->HEXCLAVE_*
rename, including a confirmed production-breaking dashboard build failure.
- dashboard/.env: empty out non-empty committed NEXT_PUBLIC_HEXCLAVE_* values
(ENABLE_DEVELOPMENT_FEATURES_PROJECT_IDS, HEAD_TAGS) that collided with the
platform-set legacy NEXT_PUBLIC_STACK_* values at build time and threw in the
inline conflict check; move the local-dev default to .env.development.
- backend polyfill: expand the ${PORT_PREFIX} sentinel for HEXCLAVE_/
NEXT_PUBLIC_HEXCLAVE_ keys too (renamed DB/Svix/S3 URLs were being skipped).
- codegen-prisma: set only HEXCLAVE_DATABASE_CONNECTION_STRING (prefer existing
HEXCLAVE/STACK, else placeholder) so it never diverges from a real STACK value
and trips prisma.config.ts's conflict check.
- backend DB tests: centralize a dual-read resolveTestDatabaseConnectionString()
and use it in bulldozer/payments suites (were legacy-STACK_-only).
- dashboard next.config: dual-read NEXT_PUBLIC_HEXCLAVE_IS_PREVIEW for the
X-Frame-Options gate.
- RDE manager: inject canonical HEXCLAVE_* names alongside legacy STACK_* ones.
- vite examples: restore VITE_HEXCLAVE_* || VITE_STACK_* fallback.
- cli auth: dual-read HEXCLAVE_API_URL / HEXCLAVE_DASHBOARD_URL.
- shared env: make getEnvVarWithHexclaveFallback two-way so canonical callers
also fall back to the legacy name; add tests.
- convex example: replace non-null assertion with ?? throwErr(...).
|
||
|---|---|---|
| .. | ||
| components/ui | ||
| hexclave | ||
| hooks | ||
| lib | ||
| pages | ||
| App.css | ||
| App.tsx | ||
| index.css | ||
| main.tsx | ||
| vite-env.d.ts | ||