chore: retire migrated GitHub Actions workflows#264
Merged
Conversation
Scheduled monitoring has cut over to the VPS (supercronic running
automation/jobs.yaml); the four GitHub schedulers and their reusable
workflow are dead weight, and the one-time migration playbook is done.
Remove them and repoint every doc that linked the deleted workflow files
at automation/jobs.yaml so no dead links remain.
- delete .github/workflows/{hourly,daily,weekly,multisig-checker}.yml and _run-monitoring.yml
- delete deploy/cutover.md and drop its pointer from deploy/runbook.md
- README.md: remove the broken workflow status badges
- timelock/SKILL.md: point the new-protocol secret step at the VPS env file
- repoint 11 protocol READMEs' schedule references to automation/jobs.yaml
Removes the GitHub Actions rollback path: the VPS is now the sole scheduler.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
What
Scheduled monitoring has cut over to the VPS (supercronic running
automation/jobs.yaml). The four GitHub schedulers + their reusable workflow were alreadydisabled_manually, and the one-time migration playbook (deploy/cutover.md) is done. This removes the dead weight and fixes all the docs that still linked the deleted workflow files.Changes
Deleted
.github/workflows/{hourly,daily,weekly,multisig-checker}.yml+_run-monitoring.yml— the retired schedulersdeploy/cutover.md— completed GitHub Actions → VPS migration playbookDocs repointed (no remaining dead links)
README.md— dropped the 3 broken workflow status badges (kept DeepWiki)timelock/SKILL.md— new-protocol secret step now points at the VPS env file /.env.exampledeploy/runbook.md— removed the cutover pointeryearn,timelock,morpho,maple,3jane,strata,cap,rtoken,usdai,utils/tenderly,fluid) — schedule references repointed from the deleted workflows toautomation/jobs.yaml; cadences preserved, dead#Lanchors droppedUntouched on purpose
ci.yml— still active CIautomation/jobs.yaml's(was .github/workflows/...)provenance notesHeads-up
This removes the GitHub Actions rollback path — the VPS becomes the sole scheduler. The safety net is now systemd
Restart=on-failure+ theautomationTelegram error channel. The four workflows had been kept disabled-not-deleted as rollback since the ~2026-06-03 cutover; this PR commits to the VPS fully.Base is
docker(the deployed branch); these files don't exist onmain, so this lands here and rides the eventualdocker→mainmerge.🤖 Generated with Claude Code