build: publish bundle with frontend 1.3.0 and backend 2.4.0 #15

Closed
opened 2026-11-02 06:20:43 +03:00 by codex-bot · 0 comments
Owner

Goal: new immutable bundle pinning published frontend:1.3.0 and backend:2.4.0 (WealthLedger/main#48 — вкладка «Концентрация»). Backend 2.4.0 содержит аддитивную миграцию TbankInstrumentClassification (CREATE TABLE), её применяет штатный deploy.sh после backup.

Acceptance criteria:

  • Images frontend:1.3.0 (sha256:f9f3a6aacbe7…) and backend:2.4.0 (sha256:2c527295c028…) are published in Nexus before the bundle tag.
  • release.env pins frontend:1.3.0 and backend:2.4.0; README states exactly what is and is not verified.
  • Existing v0.1.7 tag stays intact; annotated v0.1.8 is created on reviewed main commit after local gates (bash -n, bash tests/deploy.sh, git diff --check).

No changes to deploy.sh or production state.

Goal: new immutable bundle pinning published frontend:1.3.0 and backend:2.4.0 (WealthLedger/main#48 — вкладка «Концентрация»). Backend 2.4.0 содержит аддитивную миграцию `TbankInstrumentClassification` (CREATE TABLE), её применяет штатный `deploy.sh` после backup. Acceptance criteria: - Images frontend:1.3.0 (sha256:f9f3a6aacbe7…) and backend:2.4.0 (sha256:2c527295c028…) are published in Nexus before the bundle tag. - release.env pins frontend:1.3.0 and backend:2.4.0; README states exactly what is and is not verified. - Existing v0.1.7 tag stays intact; annotated v0.1.8 is created on reviewed main commit after local gates (`bash -n`, `bash tests/deploy.sh`, `git diff --check`). No changes to deploy.sh or production state.
Sign in to join this conversation.