cloudflare/wrangler-action
🧙♀️ easily deploy cloudflare workers applications using wrangler and github actions observed · 2026-08-28
Health v2 · maintenance only
92/100
- Activity 95
- Release rhythm 83
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 20
- age_days: 2522
- days_rel: 113
- days_push: 35
- n_releases_24m: 12
Adoption not part of the score
1928 stars · 213 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
An official GitHub Action that wraps Cloudflare's Wrangler CLI to deploy Cloudflare Workers and Pages applications directly from GitHub Actions workflows. It handles Wrangler installation, version pinning, and API token-based authentication.
Use cases
- deploy cloudflare workers on git push
- automate cloudflare pages deployment in ci
- run wrangler commands from github actions
- pin a specific wrangler version in ci
- deploy worker from a subdirectory of the repo
When to choose
- you deploy Cloudflare Workers or Pages from GitHub and want CI/CD automation
- you need managed Wrangler installation and secure API token handling in workflows
When to avoid
- you deploy to platforms other than Cloudflare
- you still rely on Wrangler v1 or global API key authentication
- you don't use GitHub Actions for CI/CD
Facets
plugin · maturity active
deployment ci-cd cli cloud-computing web-development developer-tools cloud github-actions cloudflare-workers wrangler edge-deployment serverless-deployment devops docker nodejs
1 source
- readme: https://github.com/cloudflare/wrangler-action · fetched 2026-08-28 · b3c13a10caad
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| cloudflare/wrangler-action | main | 92 |
For agents
markdown · JSON · MCP: product_card(name="cloudflare/wrangler-action")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem