release: runtime-образ UI на nginx 1.30.6 поверх принятого Эпика 3 (3.6-3.17) #100

Closed
bsodfather wants to merge 1 commits from delivery/ui-image-security-fix into main
pull from: delivery/ui-image-security-fix
Owner

Что и зачем

Security-скан runtime-образа UI блокировал публикацию контейнеров: базовый слой nginx:1.30.4-alpine3.24-slim давал 3 блокирующие HIGH-уязвимости (CVE-2026-15176, CVE-2026-93479, CVE-2026-97205, пакет nginx 1.30.4-r1, fixed 1.30.6-r0). PR поднимает только runtime-базу на patch-релиз 1.30.6; scanner, severity gate, exceptions/allowlist, CI workflows и backend не менялись.

Scope

  • Base: aed83268a0ae419b6def99375cf6bb94410da690 = ветка delivery/epic3-through-3.17 (PR #97, prerelease v0.4.0-rc.4), принятый Эпик 3 stories 3.6-3.17.
  • Дельта поверх базы: apps/ui/Dockerfile, 1 строка, runtime stage FROM nginx:1.30.4-alpine3.24-slim -> FROM nginx:1.30.6-alpine3.24-slim. Остальные pin'ы (pcre2, libcrypto3/libssl3) без изменений.
  • Story 3.18 (PR #99, code-health blocker) и 3.19 в этот PR не входят. PR #97 этим PR не закрывается и не мержится; после приёмки он либо мержится отдельно по своей защите, либо закрывается владельцем.
  • Авторство коммита сохранено за DEV (hermes-dev), DevOps добавил только публикацию.

Проверки

  • Независимая QA (same-card t_567a62e4) на неизменённом gate: base blocked (3 blocking, 0 excepted) -> fixed pass (0 blocking, 0 excepted), Trivy 0.70.0, одна свежая DB, exceptions пусты; package parity 21=21, byte parity 100 статических файлов, HTTP/health/security headers подтверждены на новом образе.
  • На этом head обязателен контекст CI / Required Checks (pull_request) (Rust/UI/Frontend E2E/Community Image Smoke, включая build+scan образов и compose up --wait).
  • Registry-образы и Gitea prerelease публикуются отдельно на annotated-теге от этого же source SHA.

Deployment

Deploy: NOT_RUN. Merge в main автоматически запускает production Deploy; для него нужен отдельно одобренный target/runbook/backup/rollback. Этот PR не мержится в рамках поставки.

## Что и зачем Security-скан runtime-образа UI блокировал публикацию контейнеров: базовый слой `nginx:1.30.4-alpine3.24-slim` давал 3 блокирующие HIGH-уязвимости (CVE-2026-15176, CVE-2026-93479, CVE-2026-97205, пакет nginx 1.30.4-r1, fixed 1.30.6-r0). PR поднимает только runtime-базу на patch-релиз 1.30.6; scanner, severity gate, exceptions/allowlist, CI workflows и backend не менялись. ## Scope - Base: `aed83268a0ae419b6def99375cf6bb94410da690` = ветка `delivery/epic3-through-3.17` (PR #97, prerelease v0.4.0-rc.4), принятый Эпик 3 stories 3.6-3.17. - Дельта поверх базы: `apps/ui/Dockerfile`, 1 строка, runtime stage `FROM nginx:1.30.4-alpine3.24-slim` -> `FROM nginx:1.30.6-alpine3.24-slim`. Остальные pin'ы (pcre2, libcrypto3/libssl3) без изменений. - Story 3.18 (PR #99, code-health blocker) и 3.19 в этот PR не входят. PR #97 этим PR не закрывается и не мержится; после приёмки он либо мержится отдельно по своей защите, либо закрывается владельцем. - Авторство коммита сохранено за DEV (`hermes-dev`), DevOps добавил только публикацию. ## Проверки - Независимая QA (same-card `t_567a62e4`) на неизменённом gate: base `blocked (3 blocking, 0 excepted)` -> fixed `pass (0 blocking, 0 excepted)`, Trivy 0.70.0, одна свежая DB, exceptions пусты; package parity 21=21, byte parity 100 статических файлов, HTTP/health/security headers подтверждены на новом образе. - На этом head обязателен контекст `CI / Required Checks (pull_request)` (Rust/UI/Frontend E2E/Community Image Smoke, включая build+scan образов и compose `up --wait`). - Registry-образы и Gitea prerelease публикуются отдельно на annotated-теге от этого же source SHA. ## Deployment Deploy: **NOT_RUN**. Merge в `main` автоматически запускает production Deploy; для него нужен отдельно одобренный target/runbook/backup/rollback. Этот PR не мержится в рамках поставки.
bsodfather added 7 commits 2026-10-25 13:10:57 +00:00
feat(epic3): deliver the accepted Epic 3 scope through Story 3.17
CI / Rust Checks (pull_request) Failing after 13m41s
CI / UI Checks (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Deploy (pull_request) Skipped
Community Release / release (push) Failing after 13m33s
54ce770682
Recovery delivery of the accumulated, TL-accepted Epic 3 work that had never been
committed to Git (stories 3.6-3.17, see the crank board). Story 3.18 is not accepted
yet and is deliberately excluded: its logging surface, its capability registration,
its oracle projections and its tests are not part of this tree.

Accepted scope
- 3.6 typed static Resource Drafts; 3.7 publication and exact binding of static
  Resource Versions; 3.8 MCP discovery/read and revocation of static Resources;
- 3.9 Resource import/export in API and UI plus TLS dependency maintenance;
  3.10 REST-backed Resource templates; 3.11 shared REST read runtime and the MCP
  revision/capability foundation;
- 3.12 parameterised Prompt Drafts with preview; 3.13 Prompt publication and exact
  version binding to Agents; 3.14 MCP prompts; 3.15 Prompt import/export;
- 3.16 composite Prompts with published Resources (dependency content scan plus
  dynamic read through the accepted 3.11 runtime, admin preview and MCP prompts/get);
- 3.17 bounded MCP completion suggestions from typed published schemas and the
  resources/list admission fix for bound template publications.

Accepted evidence being reused (unchanged code paths)
- 3.16 candidate: core 7, admin-api 22, registry 4, mcp-server 4, UI 6; one final
  `just verify` run 1651 passed / 0 failed / 2 ignored.
- 3.17 candidate: full run 1672 passed / 0 failed / 2 ignored, QA targeted reruns and
  a real MCP Inspector 2.12.0 client smoke.

Delivery engineering in this commit
- CI: one event per change (feature branches are gated by their pull request, push
  runs only on main), story events run the changed packages, the full workspace suite
  stays the feature/release gate; no cache/sharding without a measured runner check.
- Release: the packaged archives, checksums and SBOM are now uploaded to the Gitea
  release entry of the tag instead of dying with the runner workspace.

Not included on purpose: Story 3.18 work, build caches, runtime databases, local
credentials and scratch evidence.

Refs: crank kanban t_e39d7263; baseline 1b6db09bd1.
fix(ci): pass the community scope guard and publish release artifacts before registry steps
CI / Rust Checks (pull_request) Canceled after 38m52s
CI / UI Checks (pull_request) Canceled after 0s
Community Release / release (push) Canceled after 38m39s
CI / Frontend E2E (pull_request) Canceled after 0s
CI / Community Image Smoke (pull_request) Canceled after 0s
CI / Deploy (pull_request) Canceled after 0s
9567bbf3aa
- the community scope guard rejected the innocuous English comment 'One timed
  resources/list' in the Story 3.8 discovery diagnostic (its 'one-time-token'
  marker matches any 'one time' phrase). Reword the comment; no behaviour change.
- move the release artifact publication ahead of the registry/OpenBao steps, so a
  credential problem cannot leave the archives, checksums and SBOM unpublished.
ci: validate accepted stories with targeted ATDD and gate feature checks
CI / UI Checks (pull_request) Successful in 10s
CI / Rust Checks (pull_request) Failing after 25m35s
CI / Rust Feature Validation (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Failing after 1s
CI / Deploy (pull_request) Skipped
1baeefe889
ci: run the Story 3.16 composite-prompt ATDD in the story gate
CI / UI Checks (pull_request) Successful in 8s
CI / Rust Checks (pull_request) Canceled after 19m49s
CI / Rust Feature Validation (pull_request) Canceled after 0s
CI / Frontend E2E (pull_request) Canceled after 0s
CI / Community Image Smoke (pull_request) Canceled after 0s
CI / Deploy (pull_request) Canceled after 0s
CI / Required Checks (pull_request) Failing after 1s
e57ab47c05
The recovery branch publishes Story 3.16 together with Story 3.17, so the targeted story gate
must exercise both accepted user outcomes: composite Prompts with published Resources and the
bounded completion/resources-list admission of 3.17.
fix(test): isolate Valkey in the CI job network and bound readiness
CI / UI Checks (pull_request) Successful in 8s
CI / Rust Checks (pull_request) Successful in 6m1s
CI / Rust Feature Validation (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Successful in 1s
CI / Deploy (pull_request) Skipped
Community Release / release (push) Failing after 18m56s
12d8a3d490
fix(release): publish assets to the public HTTPS Gitea origin
CI / UI Checks (pull_request) Successful in 8s
CI / Rust Checks (pull_request) Successful in 6m53s
CI / Rust Feature Validation (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Successful in 1s
CI / Deploy (pull_request) Skipped
Community Release / release (push) Failing after 38m13s
aed83268a0
The release job container sees gitea.server_url as the internal
http://gitea:3000 origin, so scripts/ci-release-assets.py refused to
forward its token (run 865 failed at the publish step after packaging).
Point the publisher at https://git.itexp.me, the origin the repository
already uses for the public URL.
fix(ui): bump nginx runtime base to 1.30.6 for the image scan gate
CI / UI Checks (pull_request) Successful in 8s
CI / Rust Checks (pull_request) Successful in 6m9s
CI / Rust Feature Validation (pull_request) Skipped
CI / Frontend E2E (pull_request) Skipped
CI / Community Image Smoke (pull_request) Skipped
CI / Required Checks (pull_request) Successful in 1s
CI / Deploy (pull_request) Skipped
Community Release / release (push) Successful in 22m55s
c16b405f32
Author
Owner

Интеграция выполнена объединяющим PR #105, main 599dc1867b. Единственная дельта PR — apps/ui/Dockerfile; она побайтово совпадает с файлом main (исправление перенесено в принятую цепочку другим коммитом). Закрываю заменённую заявку; исходные ветки и теги сохраняются. Production deploy отделён от merge и не запускался.

Интеграция выполнена объединяющим PR #105, main 599dc1867b25fbe607868a324389118669c0befa. Единственная дельта PR — apps/ui/Dockerfile; она побайтово совпадает с файлом main (исправление перенесено в принятую цепочку другим коммитом). Закрываю заменённую заявку; исходные ветки и теги сохраняются. Production deploy отделён от merge и не запускался.
bsodfather closed this pull request 2026-10-26 21:37:26 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.