Skip to content

Commit 766f05d

Browse files
add changelog WIP
1 parent 81edf34 commit 766f05d

File tree

1 file changed

+52
-0
lines changed

1 file changed

+52
-0
lines changed
Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
title: Wrangler deploy - Conveniently deploy your worker with wrangler after it's been updated it in the dashboard
3+
description: Wrangler now provides a better user experience when deploying a worker that was modified via the Cloudflare dashboard.
4+
products:
5+
- workers
6+
date: 2025-11-xx
7+
---
8+
9+
import { WranglerConfig, Aside } from "~/components";
10+
11+
Now `wrangler deploy` provides a better user experience when dealing with a worker that has been modified via the Cloudflare dashboard.
12+
13+
Let's explore an example, let's say that you have a worker with the following configuration:
14+
<WranglerConfig>
15+
16+
```jsonc title="wrangler.jsonc"
17+
{
18+
"name": "my-worker",
19+
"compatibility_date": "$today",
20+
"vars": {
21+
"MY_VARIABLE_X": "A",
22+
"MY_VARIABLE_Y": "B",
23+
"MY_VARIABLE_Z": "C",
24+
},
25+
}
26+
```
27+
</WranglerConfig>
28+
29+
That you deployed via `wrangler deploy`.
30+
31+
And let's imagine that a coworker or yours of a product manager goes to the [Cloudflare dashboard worker's setting section](https://dash.cloudflare.com/?to=/:account/workers/services/view/:worker/production/settings#variables) and updates `MY_VARIABLE_X` to be `'a'`.
32+
33+
Previously running `wrangler deploy` after such Dashboard update would inform you that the worker's configuration has been updated in the dashboard and would allow you to either override the dashboard configuration or abort the operation.
34+
35+
No other information nor options would be provided to you.
36+
37+
Now in such situation you would instead be presented with a representation of what has been changed, likes so:
38+
39+
```diff
40+
"vars": {
41+
- "MY_VARIABLE_X": "A",
42+
+ "MY_VARIABLE_X": "a",
43+
"MY_VARIABLE_Y": "B",
44+
"MY_VARIABLE_Z": "C",
45+
},
46+
```
47+
48+
Allowing you to potentially override the remote settings with more understanding and confidence.
49+
50+
If you instead decide not to override the remote settings Wrangler will also offer to update the local configuration for you so that it can be realigned with the remote settings.
51+
52+
Additionally, note that this flow won't be applied for safe Wrangler deployments that are only adding settings and not removing or modifying and of the remote ones, streamlining the user's exeprience even more.

0 commit comments

Comments
 (0)