You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Beta notice: take the version from the central version source, not from .env #52
The beta banner and the beta login notice carry the version as free text in the frontend's .env on the server: BETA_BANNER_TEXT="BETA 0.5.0.0" and BETA_LOGIN_MESSAGE="... in beta for version 0.5.0.0! ..." (src/frontend/.env.local.example:16-19, read in src/frontend/lib/beta.ts:23-34). Every release has to edit the server's .env by hand, or the notice shows an old version. invoke bump-version does not touch these lines, since the .env lives on the server only.
The version already has one source: VERSION at the repository root, which invoke bump-version copies into src/frontend/package.json (and src/backend/csc_version.py). The frontend already reads it from there for the client header (src/frontend/lib/cscClient.ts:1-10, web/${pkg.version}).
Proposal:
The beta banner and the login notice take the version from the same source as cscClient.ts (package.json, set by bump-version), never from .env.
.env keeps only what is really deployment specific: BETA_PHASE (on or off) and, if wanted, the wording around the version, with a placeholder such as {version} that lib/beta.ts fills in. A text without the placeholder stays as it is.
The defaults in lib/beta.ts and the examples in .env.local.example and .env.development.local.example name the version through the placeholder, not a number.
A unit test for lib/beta.ts: the placeholder is replaced by the version from package.json.
Server note for the release: remove the version number from BETA_BANNER_TEXT and BETA_LOGIN_MESSAGE in the server's frontend .env (or use the placeholder).
Activity
fix(web): the beta banner and login notice take the version from pack…
fstwn commentedon Nov 4, 2026
Fixed in 0.6.4.4 (#53).