docs: mark weekly Forgejo package prune as enabled
Point retention table at ACTIVITY-WP-0020 closeout and live-tag protection.
This commit is contained in:
parent
c9ed0637b3
commit
b836dcecc2
1 changed files with 9 additions and 5 deletions
|
|
@ -70,14 +70,18 @@ Use for binaries, checksum files, and non-OCI release assets.
|
|||
| PyPI | same | same | Same prune lane (`pypi` type) |
|
||||
|
||||
**Protected tags:** production image tags pinned in `helm/*-values.yaml` and
|
||||
`charts/*/values.yaml` are never deleted even when outside the top 3.
|
||||
`charts/*/values.yaml`, plus **live cluster image tags** (multi-cluster
|
||||
`--live-images-file` / pod scan), are never deleted even when outside the top 3.
|
||||
|
||||
**Automation:** `activity-core` activity `weekly-forgejo-package-prune` (Sunday
|
||||
03:30 UTC). Policy: `railiance-platform/docs/forgejo-package-prune.md`.
|
||||
|
||||
Package blobs are included in daily `forgejo dump` (~1.3G with registry growth,
|
||||
2026-07-12). Restore drills must verify package metadata after isolated restore (T09).
|
||||
03:30 UTC, **enabled 2026-07-21**). Policy:
|
||||
`railiance-platform/docs/forgejo-package-prune.md`. First apply evidence:
|
||||
`railiance-platform/docs/evidence/forgejo-package-prune-apply-20260721.json`
|
||||
(38 versions deleted, 0 errors).
|
||||
|
||||
Package blobs are included in daily `forgejo dump`. Growth should slow after
|
||||
weekly prune; restore drills must still verify package metadata after isolated
|
||||
restore (T09).
|
||||
RPO/RTO for package data matches Forgejo backup policy: 24h / 4h
|
||||
(`the-custodian/docs/forgejo-production-decisions.md` § Backup).
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue