Bump the version to 1.2.0 and show it left of the logo #102

Closed
opened 2026-11-07 23:34:13 -05:00 by cmoriarty · 2 comments
Owner

Why

The repo still says 1.1.0 (backend/pyproject.toml, frontend/package.json, tag v1.1.0), but develop is 110 commits past it, with milestones 35 and 36 among them. Nothing on screen says which version is running, so there is no quick way to confirm a deploy landed.

What

  • Bump the version to 1.2.0 (new features since 1.1.0: background channels, the watch and its grades, the Watchlist page, game-night fixes), in both backend/pyproject.toml and frontend/package.json (with its lock file), through a release/1.2.0 branch as 1.1.0 was (dbe9b09), tagged v1.2.0.
  • Show the version in the top left, to the left of the logo (the h1.brand with BrandMark), on every page: Games (App.tsx), Watchlist (WatchlistPage.tsx) and Admin (AdminPage.tsx). Small, muted, tabular figures, "v1.2.0", not all-caps.
  • Hover shows the commit and build time (a develop deploy between releases keeps the same version, so the commit tells deploys apart).

Notes

  • One source for the number: the page reads it from the running server (e.g. /api/version, from the installed package's metadata plus the commit baked into the image at build time), so the page and the server can't disagree. Keep the two manifests in step with a test.
  • The image build (publish-image.yml, Dockerfile) passes the commit in as a build argument.
  • The header is shared by three pages; put the version in one component rather than three copies.
## Why The repo still says 1.1.0 (`backend/pyproject.toml`, `frontend/package.json`, tag `v1.1.0`), but develop is 110 commits past it, with milestones 35 and 36 among them. Nothing on screen says which version is running, so there is no quick way to confirm a deploy landed. ## What - **Bump the version** to 1.2.0 (new features since 1.1.0: background channels, the watch and its grades, the Watchlist page, game-night fixes), in both `backend/pyproject.toml` and `frontend/package.json` (with its lock file), through a `release/1.2.0` branch as 1.1.0 was (dbe9b09), tagged `v1.2.0`. - **Show the version in the top left, to the left of the logo** (the `h1.brand` with `BrandMark`), on every page: Games (`App.tsx`), Watchlist (`WatchlistPage.tsx`) and Admin (`AdminPage.tsx`). Small, muted, tabular figures, "v1.2.0", not all-caps. - **Hover** shows the commit and build time (a develop deploy between releases keeps the same version, so the commit tells deploys apart). ## Notes - One source for the number: the page reads it from the running server (e.g. `/api/version`, from the installed package's metadata plus the commit baked into the image at build time), so the page and the server can't disagree. Keep the two manifests in step with a test. - The image build (`publish-image.yml`, `Dockerfile`) passes the commit in as a build argument. - The header is shared by three pages; put the version in one component rather than three copies.
Author
Owner

Deployed 2026-11-08 08:48Z as 1.2.0: PR #113 (merge 654a9a7), released through release/1.2.0 (tag v1.2.0), container b0f1f361509d. The OpenSpec change settings-and-recoveries is archived in d013eb4.

Live now:

  • On every page (Games, Watchlist, Admin), v1.2.0 sits left of the logo, with the commit and build time on hover. GET /api/version answers the same.
  • The build: publish-image.yml passes the commit and build time into the image.
  • A test keeps pyproject.toml, package.json and the lock file in step.
  • The release: release/1.2.0 was merged into main and back into develop, as 1.1.0 was, and tagged v1.2.0.
    • Main's merge had one conflict, in the README's first paragraph. Your edit on main (e94ea77, "has an admin panel to show what the backend is doing") met develop's "Sports Breaker" rename, so main now carries both. Develop's README still has its own wording for that sentence.

Left open for you to check the hover on a deploy.

Deployed 2026-11-08 08:48Z as **1.2.0**: PR #113 (merge 654a9a7), released through `release/1.2.0` (tag `v1.2.0`), container b0f1f361509d. The OpenSpec change `settings-and-recoveries` is archived in d013eb4. Live now: - **On every page** (Games, Watchlist, Admin), `v1.2.0` sits left of the logo, with the commit and build time on hover. `GET /api/version` answers the same. - **The build:** `publish-image.yml` passes the commit and build time into the image. - **A test** keeps `pyproject.toml`, `package.json` and the lock file in step. - **The release:** `release/1.2.0` was merged into main and back into develop, as 1.1.0 was, and tagged `v1.2.0`. - Main's merge had one conflict, in the README's first paragraph. Your edit on main (e94ea77, "has an admin panel to show what the backend is doing") met develop's "Sports Breaker" rename, so main now carries both. Develop's README still has its own wording for that sentence. Left open for you to check the hover on a deploy.
Author
Owner

Closing: merged to develop in PR #113 (654a9a7) and released as 1.2.0 (tag v1.2.0).

Seen live on 2026-11-08: v1.2.0 left of the logo (the owner's screenshot), and /api/version answering the commit and build time.

Closing: merged to develop in PR #113 (654a9a7) and released as 1.2.0 (tag `v1.2.0`). **Seen live on 2026-11-08:** `v1.2.0` left of the logo (the owner's screenshot), and `/api/version` answering the commit and build time.
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/sports-breaker#102
No description provided.