Skip to content

Commit e2d1ab9

Browse files
Add changelog for wrangler deploy's better config conflict management (#26401)
--------- Co-authored-by: lrapoport-cf <107272160+lrapoport-cf@users.noreply.github.com>
1 parent 1f860b2 commit e2d1ab9

File tree

3 files changed

+34
-0
lines changed

3 files changed

+34
-0
lines changed
57.3 KB
Loading
28 KB
Loading
Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
title: Better local deployment flow for Cloudflare Workers
3+
description: Wrangler now provides a better user experience when deploying a worker that was previously deployed via the Cloudflare dashboard.
4+
products:
5+
- workers
6+
date: 2025-11-21
7+
---
8+
9+
import { Example } from "~/components";
10+
11+
Until now, if a Worker had been previously deployed via the [Cloudflare Dashboard](https://dash.cloudflare.com), a subsequent deployment done via the Cloudflare Workers CLI, [**Wrangler**](/workers/wrangler/)
12+
(through the [`deploy` command](/workers/wrangler/commands/#deploy)), would allow the user to override the Worker's dashboard settings without providing details on
13+
what dashboard settings would be lost.
14+
15+
Now instead, `wrangler deploy` presents a helpful representation of the differences between the [local configuration](/workers/wrangler/configuration/)
16+
and the remote dashboard settings, and offers to update your local configuration file for you.
17+
18+
See example below showing a before and after for `wrangler deploy` when a local configuration is expected to override a Worker's dashboard settings:
19+
20+
<Example title="Before">
21+
22+
![`wrangler deploy` run before the improved workflow](src/assets/images/changelog/workers/wrangler-deploy-remote-conflict-managemenet/before.png)
23+
24+
</Example>
25+
26+
<Example title="After">
27+
28+
![`wrangler deploy` run after the improved workflow](src/assets/images/changelog/workers/wrangler-deploy-remote-conflict-managemenet/after.png)
29+
30+
</Example>
31+
32+
Also, if instead Wrangler detects that a deployment would override remote dashboard settings but in an additive way, without modifying or removing any of them, it will simply proceed with the deployment without requesting any user interaction.
33+
34+
Update to [Wrangler](/workers/wrangler/) v4.50.0 or greater to take advantage of this improved deploy flow.

0 commit comments

Comments
 (0)