Merge branch 'phase-9' into config-review

2026-10-27 14:05:20 -06:00
parent 9cbfe4b996 7a43236630
commit f15d8c5fb0
5 changed files with 6 additions and 6 deletions
@@ -285,7 +285,7 @@ The real PESCO domain controllers are never used by CI. The test and production
 CI never reads VISUAL or M-Files. `deploy/ci/ci.env` sets `FEED_SOURCE=fixture`, `DRAWING_SOURCE=fixture` and `FIXTURE_DIR=/fixtures`. The image does not contain `tests/`, so the e2e job generates the fixtures on the runner before the stack starts:

 ```bash
-python -m pip install pypdf==6.21.1
+python -m pip install pypdf==6.21.2
 python -m tests.fixtures.generator --out tests/fixtures/generated
 ```

@@ -313,7 +313,7 @@ job workspace on a host directory allowed in `valid_volumes` (so the stack's bin

 ## Image rebuild for phase 9

-Phase 9 bumps two pins for security fixes found by the CI dependency scan: `pypdf` 6.21.0 to 6.21.1 and `certifi` 2026.7.22 to 2026.10.19 (`server/requirements.txt` and `pyproject.toml`). They reach a stack only with a new image. Build and tag the phase 9 commit as usual (`:sha-<sha>` from CI), set it in the stack's env file, and `up -d`. Migration 0010 runs on the way up. Then run the doctor.
+Phase 9 bumps two pins for security fixes found by the CI dependency scan: `pypdf` 6.21.0 to 6.21.2 and `certifi` 2026.7.22 to 2026.10.19 (`server/requirements.txt` and `pyproject.toml`). They reach a stack only with a new image. Build and tag the phase 9 commit as usual (`:sha-<sha>` from CI), set it in the stack's env file, and `up -d`. Migration 0010 runs on the way up. Then run the doctor.

 ## Notifications (phase 9)