Promote development → master (deploy v2: versioning + visible jobs + rollback) #106

Merged

developer merged 3 commits from development into master 2026-06-22 06:01:04 +00:00

Conversation 1 Commits 3 Files Changed 12

+459 -101

developer commented 2026-06-22 05:41:10 +00:00

Owner

Copy Link

Copy Source

Promote development → master: deploy v2 (release versioning + visible deploy jobs + manual rollback).

Builds on the live Stage 18 contour. After merge: tag v1.0.0 on master and run prod-deploy to roll the live site (currently a SHA build) up to the versioned release.

• Single semver + Go ldflags (pkg/version → service.version telemetry attr + About).
• prod-deploy split into visible jobs (build → deploy-main → deploy-bot → verify).
• New manual prod-rollback (blank = previous version, or a release tag).

Test-only CI on a master PR; prod stays manual.

Promote **development → master**: deploy v2 (release versioning + visible deploy jobs + manual rollback). Builds on the live Stage 18 contour. After merge: tag `v1.0.0` on master and run `prod-deploy` to roll the live site (currently a SHA build) up to the versioned release. - Single semver + Go ldflags (`pkg/version` → `service.version` telemetry attr + About). - `prod-deploy` split into visible jobs (build → deploy-main → deploy-bot → verify). - New manual `prod-rollback` (blank = previous version, or a release tag). Test-only CI on a master PR; prod stays manual.

developer added 3 commits 2026-06-22 05:41:10 +00:00

feat: stamp the build version into every service ... 8d45ae6e3b

pkg/version.Version (default "dev") is set at link time via -ldflags from each
service Dockerfile's VERSION build-arg, which the deploy passes as the git tag
(git describe --tags). It surfaces as the OpenTelemetry service.version resource
attribute (so Grafana/Tempo are version-aware), alongside the SPA's existing
About version. Adds the VERSION build-arg to the backend/gateway/validator/bot
compose builds and a serviceResource test covering service.name + service.version.

feat(deploy): visible prod-deploy jobs + manual prod-rollback ... c59e522732

- prod-deploy.yaml is now four visible sequential jobs (build -> deploy-main ->
  deploy-bot -> verify) so the rollout stages show in the Actions UI; the
  per-service rolling stays in the deploy-main log.
- prod-rollback.yaml: a separate manual workflow_dispatch. Leave target_version
  blank to roll back to the previous deployed version (the host now tracks
  DEPLOYED_TAG + PREVIOUS_TAG), or pick a release tag. Re-deploys an already
  published image rolling + health-gated, image-only (no rebuild, no DB migration).
- prod-deploy.sh tracks the previous tag (commit_tag) for the blank-input rollback.
- Docs: ARCHITECTURE §13 + deploy/README runbook cover versioning + rollback.

Merge pull request 'Deploy v2 — release versioning + visible deploy jobs + manual rollback' (#105) from feature/release-versioning into development 40d8f06588

owner approved these changes 2026-06-22 06:00:20 +00:00

developer merged commit 24017bcb7f into master 2026-06-22 06:01:04 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

owner

Labels

No items

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

owner (Ilia) developer

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: developer/scrabble-game#106