Skip to content

chore(octosts): remove the epoch-bot identity - #138

Merged
javacruft merged 1 commit into
mainfrom
octo-sts/chore-remove-epoch-bot-policy
Oct 23, 2026
Merged

javacruft merged 1 commit into
mainfrom
octo-sts/chore-remove-epoch-bot-policy

Conversation

@javacruft

Copy link
Copy Markdown
Member

What

Removes the epoch-bot OctoSTS trust policy for wolfi-dev/os.

Why

epoch-bot is being decommissioned in chainguard-dev/mono#71452. Neither the rulesets nor the classic branch protection on os's main branch require any status checks (checked 2026-10-22), so dropping its check blocks nothing. Once the prod deployment is destroyed, nothing exchanges tokens against this policy.

Notes

  • Merge after enforce.dev has applied mono#71452 (the next prod provision after it merges). Until then prod epoch-bot still posts on os, and removing the policy first would make every token exchange fail and alert the OS on-call channel.

🤖 Generated with Claude Code

epoch-bot is being decommissioned in chainguard-dev/mono#71452. Its
check on wolfi-dev/os is not required by branch protection, and with
the prod deployment destroyed nothing exchanges tokens against this
trust policy.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@javacruft
javacruft marked this pull request as ready for review October 22, 2026 18:12
@javacruft
javacruft merged commit 8bc8512 into main Oct 23, 2026
5 checks passed
@javacruft
javacruft deleted the octo-sts/chore-remove-epoch-bot-policy branch October 23, 2026 07:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants