Skip to content

fix: pass the records flag through the production release build - #6

Merged
dadadave80 merged 1 commit into
mainfrom
fix/release-records-flag
Nov 14, 2026
Merged

dadadave80 merged 1 commit into
mainfrom
fix/release-records-flag

Conversation

@dadadave80

Copy link
Copy Markdown
Owner

The production release build (scripts/build-release.ts + buildGameSite) defines every import.meta.env.VITE_* explicitly. VITE_RECORDS_ENABLED was missing there, so the harbor records stayed off in production even with the Vercel flag set.

This passes the flag through the same way as VITE_SEALED_NOTE_ENABLED: on only for VERCEL_ENV=production, a Privy app present, and the value exactly "true".

Verified locally: bun run test passes; a production-style build compiles records on with the flag true and off without it.
Not verified: records in a real signed-in production session. That is checked after merge.

feat/season-two-ui contains this commit too, so merge order doesn't matter.

The release build defines each VITE flag explicitly; VITE_RECORDS_ENABLED was missing, so production never included the harbor records even with the flag set. It now follows the sealed note: production only, with a Privy app, and only when exactly true.
@vercel

vercel Bot commented Nov 14, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
familiar Ready Ready Preview Nov 14, 2026 4:55am UTC

@dadadave80
dadadave80 merged commit 90cf1cc into main Nov 14, 2026
3 checks passed
@dadadave80
dadadave80 deleted the fix/release-records-flag branch November 14, 2026 05:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant