WealthLedger/deploy
5
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity

build: deploy frontend 1.1.0 and backend 2.1.0 #5

New Issue
Closed
opened 2026-10-13 07:47:25 +03:00 by codex-bot · 2 comments
codex-bot commented 2026-10-13 07:47:25 +03:00
Owner
Copy Link
Copy Source

Goal

Publish a deploy bundle that pins the released frontend 1.1.0 and backend 2.1.0 images.

Context

Component release tags are immutable and point to the accepted main commits:

  • frontend v1.1.0 at c7d8d2c8f96b4fda282cfed077d6afdf5431bcc4
  • backend v2.1.0 at 3d50db7903b54c7a2af56e31bf1edb1b37de4924

Coordinating release: WealthLedger/main#30.

Acceptance Criteria

  • release.env pins exactly frontend 1.1.0 and backend 2.1.0 images; no latest tag.
  • Deploy script tests and shell syntax checks pass on the candidate.
  • The bundle is accepted in main and published under a new annotated immutable deploy tag.
  • Production application is updated only through ./deploy.sh <deploy-tag> after the bundle and component images are verified.
## Goal Publish a deploy bundle that pins the released frontend `1.1.0` and backend `2.1.0` images. ## Context Component release tags are immutable and point to the accepted `main` commits: - frontend `v1.1.0` at `c7d8d2c8f96b4fda282cfed077d6afdf5431bcc4` - backend `v2.1.0` at `3d50db7903b54c7a2af56e31bf1edb1b37de4924` Coordinating release: WealthLedger/main#30. ## Acceptance Criteria - `release.env` pins exactly frontend `1.1.0` and backend `2.1.0` images; no `latest` tag. - Deploy script tests and shell syntax checks pass on the candidate. - The bundle is accepted in `main` and published under a new annotated immutable deploy tag. - Production application is updated only through `./deploy.sh <deploy-tag>` after the bundle and component images are verified.
codex-bot commented 2026-10-13 08:07:03 +03:00
Author
Owner
Copy Link
Copy Source

Deploy bundle published.

  • PR #6 was merged fast-forward-only.
  • Annotated tag v0.1.4 resolves to a45f750febb9f9b7de9aa6a8896a66fb9d979b6c.
  • release.env pins frontend 1.1.0 and backend 2.1.0.
  • Local gates passed: bash -n deploy.sh tests/deploy.sh, bash tests/deploy.sh, git diff --check.

Production update is intentionally not run by automation. Operator should apply ./deploy.sh v0.1.4 on the production host and record backup/smoke-test evidence here.

Deploy bundle published. - PR #6 was merged fast-forward-only. - Annotated tag `v0.1.4` resolves to `a45f750febb9f9b7de9aa6a8896a66fb9d979b6c`. - `release.env` pins frontend `1.1.0` and backend `2.1.0`. - Local gates passed: `bash -n deploy.sh tests/deploy.sh`, `bash tests/deploy.sh`, `git diff --check`. Production update is intentionally not run by automation. Operator should apply `./deploy.sh v0.1.4` on the production host and record backup/smoke-test evidence here.
codex-bot commented 2026-10-17 05:45:21 +03:00
Author
Owner
Copy Link
Copy Source

Закрыто как неактуальное по решению владельца.

Повторная проверка перед закрытием:

  • Тег v0.1.4 аннотированный и указывает на a45f750 (это же origin/main). Его release.env закрепляет frontend 1.1.0 и backend 2.1.0, latest нет.
  • Теги компонентов совпадают с контекстом issue: frontend v1.1.0 на c7d8d2c, backend v2.1.0 на 3d50db7. Версии в package.json совпадают.
  • На v0.1.4 в чистом worktree: bash -n deploy.sh tests/deploy.sh, bash tests/deploy.sh и git diff --check прошли.

Не выполнялось и не подтверждено:

  • Production через ./deploy.sh v0.1.4 не обновлялся, backup и smoke-тест не зафиксированы.
  • Образы 1.1.0 и 2.1.0 в Nexus (pull, OCI revision, amd64) я не проверял.
  • README внутри неизменяемого v0.1.4 ещё говорит про v0.1.3 и версии 1.0.0 и 2.0.0. Исправить можно только в следующем комплекте.
Закрыто как неактуальное по решению владельца. Повторная проверка перед закрытием: - Тег `v0.1.4` аннотированный и указывает на `a45f750` (это же `origin/main`). Его `release.env` закрепляет frontend `1.1.0` и backend `2.1.0`, `latest` нет. - Теги компонентов совпадают с контекстом issue: frontend `v1.1.0` на `c7d8d2c`, backend `v2.1.0` на `3d50db7`. Версии в `package.json` совпадают. - На `v0.1.4` в чистом worktree: `bash -n deploy.sh tests/deploy.sh`, `bash tests/deploy.sh` и `git diff --check` прошли. Не выполнялось и не подтверждено: - Production через `./deploy.sh v0.1.4` не обновлялся, backup и smoke-тест не зафиксированы. - Образы `1.1.0` и `2.1.0` в Nexus (pull, OCI revision, amd64) я не проверял. - README внутри неизменяемого `v0.1.4` ещё говорит про `v0.1.3` и версии `1.0.0` и `2.0.0`. Исправить можно только в следующем комплекте.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Medium
3
The priority is medium
Priority
Low
4
The priority is low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Status
Abandoned
3
Somebody has started to work on this but abandoned work
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
codex-bot hermes-agent ksv741 publisher-bot renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: WealthLedger/deploy#5