chore(secrets): record the 2026-10-13 rotations in the manifest #143

Merged
jfraeys merged 1 commit from jfraeys/chore/manifest-rotated-2026-10-13 into main 2026-10-13 21:04:21 -04:00
Owner

Manifest-only (no secret value read or written). Sets rotated_at: 2026-10-13 for the 8 keys PR #125 lists plus POSTFIX_SENDER_ALERTS_APIKEY (#133). Three had a stale 2026-10-09; six had null.

Expiry report: unknown 48 -> 44, ok 13 -> 18.

Also settles the P8 reconcile item: AUTHELIA_OIDC_PRIVATE_KEY_PEM manifest date 2026-10-10 is generation; docs' 2026-10-13 was the PR #52 merge/redeploy. Not a conflict; the remediation row now says both.

Not changed on purpose: the other 44 unknown entries have no rotation evidence, and the ones with no schedule need a policy decision (rotate_every_days / expiry), not a recorded fact.

🤖 Generated with Claude Code

Manifest-only (no secret value read or written). Sets `rotated_at: 2026-10-13` for the 8 keys PR #125 lists plus `POSTFIX_SENDER_ALERTS_APIKEY` (#133). Three had a stale 2026-10-09; six had null. Expiry report: unknown 48 -> 44, ok 13 -> 18. Also settles the P8 reconcile item: `AUTHELIA_OIDC_PRIVATE_KEY_PEM` manifest date 2026-10-10 is generation; docs' 2026-10-13 was the PR #52 merge/redeploy. Not a conflict; the remediation row now says both. Not changed on purpose: the other 44 unknown entries have no rotation evidence, and the ones with no schedule need a policy decision (rotate_every_days / expiry), not a recorded fact. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
chore(secrets): record the 2026-10-13 rotations in the manifest
All checks were successful
Secret scan / scan (pull_request) Successful in 13s
4e94c68f80
PR #125 rotated eight Vaultwarden/Authelia secrets and #133 replaced
POSTFIX_SENDER_ALERTS_APIKEY, all on 2026-10-13. Three still carried the
2026-10-09 date and six had none. Expiry report: unknown 48 -> 44, ok 13 -> 18.

Also clarify the remediation row for AUTHELIA_OIDC_PRIVATE_KEY_PEM: the key was
generated 2026-10-10 (the manifest's rotated_at); 2026-10-13 is the PR #52
merge and redeploy, so the two dates were never in conflict.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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!143
No description provided.