zeekayandHanzo Dev 4cb0c9b811 rename EVENT_INGEST_KEY -> PUBLISHABLE_KEY ...

The value is a pk- prefixed PUBLISHABLE key -- the Stripe vocabulary, and the
thing the Dockerfile gate already tests for. Naming it EVENT_INGEST_KEY hid
that: the old gate read 'EVENT_INGEST_KEY is not a publishable key', naming
one thing two ways in a single sentence.

One substitution covers all three spellings, since the framework prefixes
wrap the same token:
  EVENT_INGEST_KEY            -> PUBLISHABLE_KEY              (KMS name + build-arg)
  NEXT_PUBLIC_EVENT_INGEST_KEY -> NEXT_PUBLIC_PUBLISHABLE_KEY (Next inlines NEXT_PUBLIC_*)
  VITE_EVENT_INGEST_KEY        -> VITE_PUBLISHABLE_KEY        (Vite inlines VITE_*)

KMS already carries deploy/PUBLISHABLE_KEY (env prod) with the same value,
written and read back before this landed, so no build can reach a name that
does not exist yet. The old KMS entry stays until every repo is renamed, then
it goes -- one name, no alias.

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-05 16:22:18 -07:00

..

src

rename EVENT_INGEST_KEY -> PUBLISHABLE_KEY

2026-08-05 16:22:18 -07:00

package.json

deps: one set of versions, and a transpile list that actually applies

2026-07-31 17:41:08 -07:00

tsconfig.json

feat(analytics): every docs site on the ONE /v1/event door, not the Umami tag

2026-07-25 13:34:22 -07:00

tsdown.config.ts

feat(analytics): every docs site on the ONE /v1/event door, not the Umami tag

2026-07-25 13:34:22 -07:00