Automate RC8 release journeys
GeoIntel release gates / Compile, test, contracts and builds (push) Canceled after 0s
GeoIntel release gates / Python and npm vulnerability policy (push) Canceled after 0s
GeoIntel release gates / GIS image, SBOM and container scan (push) Canceled after 0s

This commit is contained in:
Codex
2026-07-18 06:07:44 +02:00
parent 0fae53a7de
commit 55685ba1bd
22 changed files with 2665 additions and 11 deletions
+31
View File
@@ -1889,3 +1889,34 @@ python scripts/verify_python_lock.py
The complete gate and vulnerability/SBOM policy are documented in
`docs/CI_SUPPLY_CHAIN.md`.
## Release golden areas
The RC browser suite uses seven deterministic, bounded regression areas across
Belgium and the Belgian North Sea. Preview the required changes without
mutating the runtime:
```bash
python scripts/provision_release_golden_areas.py \
--base-url http://127.0.0.1:8000 \
--output artifacts/rc8-golden-areas.json
```
Create only missing Areas through the canonical project/area APIs:
```bash
python scripts/provision_release_golden_areas.py \
--base-url http://127.0.0.1:8000 \
--output artifacts/rc8-golden-areas.json \
--apply
```
The operator copies the governed Mol and Kempen geometries into the national
workbench with their source project/Area identifiers and provisions bounded
Wallonia, Brussels, language-boundary, coast and offshore multi-zone Areas.
Every geometry receives a deterministic SHA-256 fingerprint in the evidence
file. It never imports provider data or writes directly to database tables.
Explicit demo seeding also reactivates its own archived technical project.
This keeps the opt-in fixture workflow selectable without changing the normal
active-project lifecycle.