build: publish bundle with frontend 2.0.0 and backend 3.0.0 #19

Open
opened 2026-11-13 08:58:08 +03:00 by codex-bot · 1 comment
Owner

Goal: immutable deployment bundle pinning the compatible RUB-only component releases frontend v2.0.0 and backend v3.0.0 (WealthLedger/main#54, WealthLedger/main#55).

Acceptance criteria:

  • Both immutable component images have successful publication workflows before bundle tag.
  • release.env pins exactly frontend:2.0.0 and backend:3.0.0; README records compatibility, migration data effects and rollback boundary, with unverified production behavior explicit.
  • Existing v0.1.9 remains intact. A new annotated bundle tag is created on reviewed main commit after local checks (bash -n, bash tests/deploy.sh, git diff --check).
  • No production deployment without server access and operational confirmation.
Goal: immutable deployment bundle pinning the compatible RUB-only component releases frontend v2.0.0 and backend v3.0.0 (WealthLedger/main#54, WealthLedger/main#55). Acceptance criteria: - Both immutable component images have successful publication workflows before bundle tag. - release.env pins exactly frontend:2.0.0 and backend:3.0.0; README records compatibility, migration data effects and rollback boundary, with unverified production behavior explicit. - Existing v0.1.9 remains intact. A new annotated bundle tag is created on reviewed main commit after local checks (`bash -n`, `bash tests/deploy.sh`, `git diff --check`). - No production deployment without server access and operational confirmation.
Author
Owner

Published deploy bundle v0.1.10 on reviewed main commit 2ff8ba9c (PR #20), pinning published frontend 2.0.0 and backend 3.0.0. Local checks: bash -n deploy.sh tests/deploy.sh, bash tests/deploy.sh, git diff --check passed; component OpenAPI JSON identical. Docker daemon/server unavailable here, so real Docker restore and production deployment/smoke remain unverified. Run ./deploy.sh v0.1.10 on the Linux host only after confirming the pre-migration backup/recovery plan; backend migration removes legacy snapshots and non-RUB history.

Published deploy bundle `v0.1.10` on reviewed main commit `2ff8ba9c` (PR #20), pinning published frontend `2.0.0` and backend `3.0.0`. Local checks: `bash -n deploy.sh tests/deploy.sh`, `bash tests/deploy.sh`, `git diff --check` passed; component OpenAPI JSON identical. Docker daemon/server unavailable here, so real Docker restore and production deployment/smoke remain unverified. Run `./deploy.sh v0.1.10` on the Linux host only after confirming the pre-migration backup/recovery plan; backend migration removes legacy snapshots and non-RUB history.
Sign in to join this conversation.