stack/packages
Bilal Godil 1ede37281f Don't ship env-var conflict-throw in generated customer SDK
The generated env.ts getters ship inside @hexclave/stack / @hexclave/react
and are read on a hot, side-effect-free path by SDK consumers. The
conflict-detection helper added with the HEXCLAVE_* rename made those getters
throw when both a HEXCLAVE_* and STACK_* spelling were set to different values
— a breaking change to env-var reading for SDK users.

Revert the generated getters to a plain || dual-read chain (prefer HEXCLAVE_*,
fall back to legacy STACK_*, empty-as-unset), with no throw. Conflict detection
stays in our own non-shipped infra only (packages/shared getEnvVariable/
getProcessEnv, dashboard inline env, CLI auth, docker entrypoint).

Order-preserving dedup of the candidate list is kept so HEXCLAVE_API_URL no
longer emits its STACK_URL aliases twice.
2026-06-16 17:56:47 -07:00
..
cli Merge branch 'dev' into rename-env-vars-hexclave 2026-06-16 17:46:50 -07:00
dashboard-ui-components chore: update package versions 2026-06-16 19:32:53 +00:00
js chore: update package versions 2026-06-16 19:32:53 +00:00
next chore: update package versions 2026-06-16 19:32:53 +00:00
react chore: update package versions 2026-06-16 19:32:53 +00:00
sc chore: update package versions 2026-06-16 19:32:53 +00:00
shared Merge branch 'dev' into rename-env-vars-hexclave 2026-06-16 17:46:50 -07:00
shared-backend chore: update package versions 2026-06-16 19:32:53 +00:00
tanstack-start chore: update package versions 2026-06-16 19:32:53 +00:00
template Don't ship env-var conflict-throw in generated customer SDK 2026-06-16 17:56:47 -07:00
ui feat: add custom OIDC provider support (team plan+ only) (#1594) 2026-06-16 16:35:11 -07:00