cloudflare-workers-cd-rollback

Automate Cloudflare Workers deployment with rollback on smoke test failure.

320|3|Updated Apr 24, 2026

Search Tags:#workflow #cloudflare #deploy #github-actions #ci-cd #workers #auto-rollback

Ready to run

npx skills add https://github.com/mizchi/skills --skill cloudflare-workers-cd-rollback

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cloudflare-workers-cd-rollback
Source: https://github.com/mizchi/skills/tree/main/devops/workers-cd-rollback
Command: npx skills add https://github.com/mizchi/skills --skill cloudflare-workers-cd-rollback

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

GitHub Actions CD for a Cloudflare Worker with auto-rollback on smoke failure. Use when you want push-to-deploy with safety: capture pre-deploy version, deploy, smoke, rollback if smoke fails.

Core Features & Use Cases

Reusable workflows for deploy, staging, and production with precheck gating to ensure credentials are present.
Pre-deploy version capture and deterministic rollback targets, so you can revert to the last known good version on failure.
End-to-end CD pipeline: apply D1 migrations, build, deploy to Cloudflare Workers, run smoke tests, and auto-rollback on smoke failures.
Environment awareness: separate staging and production flows with appropriate environment flags and reporting.

Quick Start

Initiate a safe push-to-deploy by triggering the deploy workflow for a target environment, which will capture the current version, run migrations, deploy, smoke, and rollback on failure.

Frequently Asked Questions about cloudflare-workers-cd-rollback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up auto-rollback for Cloudflare Workers deployments in GitHub Actions?▼

Auto-rollback for Cloudflare Workers deployments is handled by capturing the pre-deploy version, deploying, running smoke tests, and automatically reverting to the previous version if the smoke checks fail. This pipeline is fully automated via GitHub Actions.

What is the safest way to automate a push-to-deploy workflow for Cloudflare Workers?▼

The safest push-to-deploy workflow for Cloudflare Workers captures a deterministic pre-deploy version, applies D1 migrations, builds, deploys, and runs smoke tests. It automatically rolls back to the last known good version upon smoke failure.

Can I run separate staging and production deployment workflows for Cloudflare Workers?▼

Yes, you can run separate staging and production deployment workflows for Cloudflare Workers. These environment-specific flows use appropriate environment flags, precheck gating, and rollback reporting to ensure traceability and safety.

How does a CI/CD pipeline handle D1 migrations before deploying Cloudflare Workers?▼

A CI/CD pipeline handles D1 migrations by applying them as part of the end-to-end deployment workflow before building and deploying Cloudflare Workers. This ensures database schemas are updated safely before the application goes live.

Why does my Cloudflare Workers deployment fail and how do I revert to a previous version?▼

Cloudflare Workers deployments fail when post-deploy smoke tests detect errors. You revert by automatically rolling back to the captured pre-deploy version, which is the last known good deployment target.

Do I need separate credentials for staging and production Cloudflare Workers environments?▼

Yes, staging and production environments require separate credentials. The reusable deployment workflows include precheck gating to ensure the correct environment-specific credentials are present before proceeding with the build and deploy.