coulomb/activity-core
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(release): attended releases commit the railiance-platform child pin
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 244572@bnt-lap001
Assistant-Session: 3b235e1a-ae45-4d0f-ae70-17a9bd78ece8
This commit is contained in:
tegwick 2026-10-20 00:05:34 +02:00
parent 4498b89c11
commit bbe2081a2e
1 changed files with 8 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/gitops-release.md
View file

@ -65,6 +65,14 @@ promotion and failed-health rollback before claiming unattended operation.
The 24-hour observation begins with the recorded successful adoption; a stateful
failure or unintended spec change invalidates that observation.
An attended release must also commit the new child `targetRevision` to
`railiance-platform/argocd/railiance01/applications/activity-core.application.yaml`.
Patching the live Application alone is not enough: `railiance-apps-root` is
synced by hand from that file, and a stale pin there rolls activity-core back on
the next root sync. The 2026-10-04 and 2026-10-19 releases skipped this step,
and RPF-WP-ADHOC-2026-10-19 repaired it. Close the release only after
`make argocd-pin-drift` in railiance-platform reports `ok` for activity-core.
## Live proof and current gates
The 2026-09-27 adoption and subsequent digest release are complete and healthy.