cloudflare-workers-ci-cd

# Cloudflare Workers CI/CD **Status**: ✅ Production Ready | Last Verified: 2025-01-27 **GitHub Actions**: v4 | **GitLab CI**: Latest | **Wrangler**: 4.50.0 ## Table of Contents - [What Is Workers CI/CD?](#what-is-workers-cicd) - [New in 2025](#new-in-2025) - [Quick Start (10 Minutes)](#quick-start-10-minutes) - [Critical Rules](#critical-rules) - [Core Concepts](#core-concepts) - [Top 5 Use Cases](#top-5-use-cases) - [Best Practices](#best-practices) - [Top 7 Errors Prevented](#top-7-errors-prevented) - [When to Load References](#when-to-load-references) --- ## What Is Workers CI/CD? Automated testing and deployment of Cloudflare Workers using **GitHub Actions** or **GitLab CI**. Enables running tests on every commit, deploying to preview/staging/production environments automatically, managing secrets securely, and implementing deployment gates for safe releases. **Key capabilities**: Automated testing, multi-environment deployments, preview URLs per PR, secrets management, deployment verification, automatic rollbacks. --- ## New in 2025 **GitHub Actions Updates** (January 2025): - **NEW**: `cloudflare/wrangler-action@v4` (improved caching, faster deployments) - **IMPROVED**: Secrets support with `vars` and `secrets` parameters - **ADDED**: Built-in preview environment cleanup - **BREAKING**: `apiToken` renamed to `api-token` (kebab-case) **Migration from v3**: ```yaml # ❌ OLD (v3) - uses: cloudflare/wrangler-action@3 with: apiToken: ${{ secrets.CLOUDFLARE_AP...