Create workflow for updating Cloudflare release version
Open
Nobody has claimed this yet.
p2
refactor
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
In the event of a major interface bug, it is sometimes desirable to quickly point Cloudflare to an older (e.g. yesterday's) stable version of the interface.
We should create a workflow for this task so the team can safely and reliably execute it while senior engineers are out of office.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository’s existing release workflows and the Cloudflare deployment process. Define how an older stable interface version is selected, verified, and restored safely; done means the team can execute and validate the rollback without senior engineers present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- cloud, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100