Summary
Cloudflare Artifacts repositories can now run a CI/CD pipeline automatically on every push. Developers define a CI Workflow with the new CI SDK that builds, lints, type-checks, and tests code, caches dependencies when lockfiles are unchanged, blocks deployment on build failure, and ships to Workers.
What changed
Artifacts repos gained automatic build-and-deploy on push. A CI Workflow defined with the CI SDK triggers on Artifacts push events, runs linting/type-checking/tests, caches dependency installs across unchanged lockfiles, halts deploy on failure, and uses scoped API tokens limited to the deployment phase to target Workers.
Why it matters
This turns Cloudflare's Artifacts code hosting into an end-to-end deploy pipeline, reducing reliance on external CI like GitHub Actions for teams already building on Workers. Push-to-deploy plus scoped deploy tokens tightens the loop between source control and production on a single platform.
Evidence excerpt
run your CI/CD pipeline on your Artifacts repo by defining a CI Workflow with the CI SDK, automatically triggered on Artifacts push events.