Repository navigation
Add CI secrets maintenance note - #773
Merged
Merged
Conversation
Documents API_TOKEN_GITHUB and OSSRH_* secrets, how to regenerate them, and an expiry log to fill in on each rotation. Written up after API_TOKEN_GITHUB silently expired for three months (2026-07-02 to 2026-10-01) with every CI run reporting green the whole time. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
4 tasks
Contributor
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The secret inventory is inaccurate and the initial rotation still lacks the expiry date the document is intended to track.
Review effort: Balanced
Findings: 2
Open (2)
What changed in this PR
Documents CI secret ownership, rotation steps, and the recent token-expiry incident.
Changes:
- Adds secret usage and regeneration guidance.
- Adds an expiry log and incident history.
| File | Description |
|---|---|
.github/SECRETS.md |
Documents CI secrets and token maintenance. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
eitch
previously approved these changes
Oct 1, 2026
Updated usage of secrets in CI workflows for better clarity and added relevant files. Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…' into docs/ci-secrets-maintenance-note
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.




Summary
Adds
.github/SECRETS.mddocumentingAPI_TOKEN_GITHUBandOSSRH_*, how to regenerateAPI_TOKEN_GITHUB, and an expiry log to fill in on each rotation.Written up after
API_TOKEN_GITHUBsilently expired for three months (2026-07-02 → 2026-10-01) — everyci-main-snapshot.ymlrun reported green the whole time because the push-retry loop never checked for final failure (fixed separately in #772). Nobody had a record of what the token was for, where to regenerate it, or when it was last rotated, which made this much harder to diagnose than it needed to be.Companion to a tracking issue for next year's renewal.
🤖 Generated with Claude Code