ci-cd cloudflare-workflows typescript artifacts devops

Cloudflare ships CI SDK built on Workflows

Define CI/CD pipelines in TypeScript instead of YAML, trigger directly on artifact push, cache dependencies across steps with native observability in Workflows dashboard.

Summary

Eliminates event subscription/queue boilerplate for triggering CI jobs and replaces YAML with TypeScript for full customization. Dependency caching and parallel step execution reduce pipeline latency while platform teams can now share one CI definition across all customer repos.

Why it matters

Implementation verdict

Replaces GitHub Actions for Cloudflare-hosted code. Requires: Artifacts repo, wrangler config with events field, @cloudflare/ci SDK import, TypeScript workflow definition. Ready to try now for new Cloudflare-native projects; migration from Actions is feasible but not a drop-in replacement.

Sources

1.We have stitched the store, build, and deploy steps together with the CI SDK, built on Cloudflare Workflows
2.A CI/CD pipeline is just a Workflow
3.Instead of YAML, you can define your CI/CD pipeline in Typescript for greater customization and configurability
4.you can now kick off a CI job directly on push instead of configuring an event subscription, a queue, and a queue consumer
5.Dependency caching reduces the latency of your CI/CD pipeline since every CI step won't need to rerun the install
6.Each CI run surfaces as a Workflow instance so you can view its step-by-step execution and observability directly in the Workflows dashboard

Dev Signal

Get briefs like this in your inbox — free, every weekday.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs