fix: unblock backend image build with current Debian packages #129

Closed
opened 2026-10-24 20:47:00 +03:00 by codex-bot · 0 comments
Owner

Backend v2.3.0 tag image job 1616 fails before publish: apt-get install in Dockerfile requests ca-certificates=20250419~deb12u1, absent from current bookworm package index. Frontend v1.2.1 image has been published; deploy v0.1.6 pins unavailable backend image.

Acceptance Criteria:

  • Backend production/dependencies Dockerfile stages install required packages using available Bookworm packages without fragile exact apt versions from mutable repositories.
  • Backend image release workflow builds and publishes a new immutable patch version with matching revision, smoke and CI checks.
  • A new deploy bundle points at the successfully published backend image; existing v2.3.0 and deploy v0.1.6 tags stay intact.

Related deploy#12 and main#44.

Backend v2.3.0 tag image job 1616 fails before publish: `apt-get install` in Dockerfile requests ca-certificates=20250419~deb12u1, absent from current bookworm package index. Frontend v1.2.1 image has been published; deploy v0.1.6 pins unavailable backend image. Acceptance Criteria: - Backend production/dependencies Dockerfile stages install required packages using available Bookworm packages without fragile exact apt versions from mutable repositories. - Backend image release workflow builds and publishes a new immutable patch version with matching revision, smoke and CI checks. - A new deploy bundle points at the successfully published backend image; existing v2.3.0 and deploy v0.1.6 tags stay intact. Related deploy#12 and main#44.
ksv741 referenced this issue from a commit 2026-10-24 21:32:58 +03:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: WealthLedger/backend#129