Deployments bring change tracking to Workers
Cloudflare has introduced Deployments for Workers, a new feature that gives developers a record of every change made to a Worker’s code, configuration, and bindings. The goal is straightforward: provide an audit trail for production applications so teams can see not just what changed, but who changed it, when, and from where.
This is positioned as a foundation for more advanced capabilities down the road, including automated deployments, rollbacks, and version control integration. Those features aren’t available yet, but the groundwork is now in place.
What gets tracked
Deployments capture changes made through any of the supported interfaces: wrangler, the Cloudflare dashboard, the API, or Terraform. That includes code updates, changes to resource bindings and environment variables, and modifications to Worker configuration such as the name or usage model.
Each deployment record includes the author, the source of the change, and a timestamp. Source tracking is meant to help teams spot anomalies — for example, if a CI job is supposed to be the only thing deploying and someone makes a change through the dashboard, that’s easy to flag and investigate.
The deployment information is available in several places. In the Cloudflare dashboard, it appears under the Worker’s Deployments tab, while the active version is shown on the Worker’s detail page. wrangler publish now reports the latest deployed version, and a new wrangler deployments command displays the full deployment history.
Also included
Deployments is available today as an open beta. Cloudflare is planning enhancements such as rollbacks, deployment status indicators, deployment rules, and a view-only mode for historical deployments. Version control integrations with services like GitHub, Bitbucket, and GitLab are also on the roadmap, which would enable automated deployments triggered by repository commits. For feedback or discussion, Cloudflare is pointing developers to its Discord and a dedicated feedback channel.
More details are available in the Developer Documentation.
