chore(rt-v1): retire promote-release-candidate.yaml (DEVEX-1656)#151
Conversation
RT v2 has landed successfully and the retirement criteria in docs/promote-release-candidate-retirement.md (in encodium/actions) are met. The retirement doc originally called for three PRs: webstore + internal_api per-caller cleanup, plus this delete. Both callers are already gone — Start Release Train.yaml doesn't exist in webstore or internal_api. So this is just the delete. Verified no other callers via per-workflow grep across all 22 RT participants + encodium/.github + encodium/actions. Nothing invokes this file. Rollback: revert this PR. RT v1 was never destructive — the legacy rc branches, *-main.N tags in git history, and the mathieudutour release_branches overrides in each participant continue to exist even without this orchestrator. The workflow was purely orchestration on top of state that lives elsewhere. Companion work landing in parallel: - Participant workflow sweep (rc gate removal + Jellyfish scrub) — 22 draft PRs (DEVEX-1653 retire) - encodium/terraform rc block removal for manage + internal_api — DEVEX-1653 retire-rc-branches PR (draft) - rc branch deletion via gh api after the sweep merges - Delete jellyfish-deploy-notification.yaml after per-repo jellyfish jobs are gone (blocked on sweep merge)
PR SummaryLow Risk Overview That workflow previously resolved the latest (or explicit) Per the PR context, callers were already removed from participant repos; this change only deletes the shared workflow definition. Reviewed by Cursor Bugbot for commit 60a4fe6. Bugbot is set up for automated code reviews on this repo. Configure here. |
Context
RT v2 has landed successfully. Retiring the v1 promote orchestrator per docs/promote-release-candidate-retirement.md in encodium/actions.
Simplified from the retirement doc
The retirement doc originally called for three PRs — two per-caller cleanup (webstore + internal_api
Start Release Train.yaml) plus this delete. Both callers are already gone —Start Release Train.yamldoesn't exist in webstore or internal_api. So this collapses to one PR: the delete.Verified via per-workflow grep across all 22 RT participants plus encodium/.github and encodium/actions. Nothing invokes this file.
Rollback
Revert this PR. RT v1 was never destructive — the legacy
rcbranches,*-main.Ntags in git history, and mathieudutourrelease_branchesoverrides in each participant continue to exist even without this orchestrator. This workflow was purely orchestration on top of state that lives elsewhere.Companion work
rcgate references + Jellyfish notify jobs (in-flight — see task ci: update docker layer caching action #59 in the sweep report)rcbranch + protection blocks for manage + internal_api (draft)jellyfish-deploy-notification.yamlafter every caller PR lands