chore(secrets): rotated forgejo #168

Merged
jfraeys merged 1 commit from chore/rotate-forgejo-20261014-185806 into main 2026-10-14 19:02:31 -04:00
Owner

Vault change from rotating forgejo on 2026-10-14 (opened by scripts/secrets/vault-pr.py). Encrypted file only; no values appear here.

Keys rotated (names only): FORGEJO_METRICS_TOKEN

Manifest: rotated_at: 2026-10-14 for FORGEJO_METRICS_TOKEN.

Not deployed. Merging changes no running service and starts no staging run. After merging: git pull, then deploy as the rotation output says (secrets shared by two services go out together).

Vault change from rotating **forgejo** on 2026-10-14 (opened by `scripts/secrets/vault-pr.py`). Encrypted file only; no values appear here. **Keys rotated (names only):** FORGEJO_METRICS_TOKEN **Manifest:** `rotated_at: 2026-10-14` for FORGEJO_METRICS_TOKEN. **Not deployed.** Merging changes no running service and starts no staging run. After merging: `git pull`, then deploy as the rotation output says (secrets shared by two services go out together).
chore(secrets): rotated forgejo
All checks were successful
Secret scan / scan (pull_request) Successful in 12s
ae2f3c43fe
Keys rotated (names only): FORGEJO_METRICS_TOKEN.
Manifest rotated_at set to 2026-10-14 for: FORGEJO_METRICS_TOKEN.

Encrypted file only; no values here. Not deployed: merging changes no running service.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jfraeys/infra!168
No description provided.