From 9401ad126400049315107830c1b48b7899d25c2e Mon Sep 17 00:00:00 2001 From: Eric Clemmons Date: Thu, 9 Jul 2026 22:08:41 -0500 Subject: [PATCH 1/4] [Workers] Mention Flagship in automatic provisioning docs --- .../docs/workers/wrangler/configuration.mdx | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/src/content/docs/workers/wrangler/configuration.mdx b/src/content/docs/workers/wrangler/configuration.mdx index 7ad44c36d05..14e45e0dd58 100644 --- a/src/content/docs/workers/wrangler/configuration.mdx +++ b/src/content/docs/workers/wrangler/configuration.mdx @@ -104,7 +104,7 @@ Further, there are a few keys that can _only_ appear at the top-level. Wrangler can automatically provision resources for you when you deploy your Worker without you having to create them ahead of time. -This currently works for KV, R2, and D1 bindings. +This currently works for KV, R2, D1, and [Flagship](/flagship/) bindings. To use this feature, add bindings to your configuration file _without_ adding resource IDs, or in the case of R2, a bucket name. Resources will be created with the name of your worker as the prefix. @@ -1855,19 +1855,19 @@ A common example of using a redirected configuration is where a custom build too ```jsonc { - "$schema": "./node_modules/wrangler/config-schema.json", - "name": "my-worker", - "main": "src/index.ts", - "vars": { - "MY_VARIABLE": "production variable", - }, - "env": { - "staging": { - "vars": { - "MY_VARIABLE": "staging variable", - }, - }, - }, + "$schema": "./node_modules/wrangler/config-schema.json", + "name": "my-worker", + "main": "src/index.ts", + "vars": { + "MY_VARIABLE": "production variable", + }, + "env": { + "staging": { + "vars": { + "MY_VARIABLE": "staging variable", + }, + }, + }, } ``` From 73a0ab913d2d8f1bdb191a2e02f75a1e7fabf3fe Mon Sep 17 00:00:00 2001 From: Eric Clemmons Date: Thu, 9 Jul 2026 22:09:44 -0500 Subject: [PATCH 2/4] [Workers] Keep Flagship provisioning update focused --- .../docs/workers/wrangler/configuration.mdx | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/src/content/docs/workers/wrangler/configuration.mdx b/src/content/docs/workers/wrangler/configuration.mdx index 14e45e0dd58..2927a3f05c1 100644 --- a/src/content/docs/workers/wrangler/configuration.mdx +++ b/src/content/docs/workers/wrangler/configuration.mdx @@ -1855,19 +1855,19 @@ A common example of using a redirected configuration is where a custom build too ```jsonc { - "$schema": "./node_modules/wrangler/config-schema.json", - "name": "my-worker", - "main": "src/index.ts", - "vars": { - "MY_VARIABLE": "production variable", - }, - "env": { - "staging": { - "vars": { - "MY_VARIABLE": "staging variable", - }, - }, - }, + "$schema": "./node_modules/wrangler/config-schema.json", + "name": "my-worker", + "main": "src/index.ts", + "vars": { + "MY_VARIABLE": "production variable", + }, + "env": { + "staging": { + "vars": { + "MY_VARIABLE": "staging variable", + }, + }, + }, } ``` From 073d98de7965f7d83014ed8105047ea668f40458 Mon Sep 17 00:00:00 2001 From: Eric Clemmons Date: Thu, 9 Jul 2026 22:16:11 -0500 Subject: [PATCH 3/4] [Workers] Remove Flagship documentation link --- src/content/docs/workers/wrangler/configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/workers/wrangler/configuration.mdx b/src/content/docs/workers/wrangler/configuration.mdx index 2927a3f05c1..8ab77f2b1b1 100644 --- a/src/content/docs/workers/wrangler/configuration.mdx +++ b/src/content/docs/workers/wrangler/configuration.mdx @@ -104,7 +104,7 @@ Further, there are a few keys that can _only_ appear at the top-level. Wrangler can automatically provision resources for you when you deploy your Worker without you having to create them ahead of time. -This currently works for KV, R2, D1, and [Flagship](/flagship/) bindings. +This currently works for KV, R2, D1, and Flagship bindings. To use this feature, add bindings to your configuration file _without_ adding resource IDs, or in the case of R2, a bucket name. Resources will be created with the name of your worker as the prefix. From 422a92299d129f3bad7d61ccececfdcc76aec22d Mon Sep 17 00:00:00 2001 From: Eric Clemmons Date: Thu, 9 Jul 2026 22:19:24 -0500 Subject: [PATCH 4/4] [Workers, Flagship] Announce automatic provisioning --- ...-07-09-flagship-automatic-provisioning.mdx | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 src/content/changelog/workers/2026-07-09-flagship-automatic-provisioning.mdx diff --git a/src/content/changelog/workers/2026-07-09-flagship-automatic-provisioning.mdx b/src/content/changelog/workers/2026-07-09-flagship-automatic-provisioning.mdx new file mode 100644 index 00000000000..bb48ff89560 --- /dev/null +++ b/src/content/changelog/workers/2026-07-09-flagship-automatic-provisioning.mdx @@ -0,0 +1,28 @@ +--- +title: Automatic provisioning for Flagship bindings +description: Wrangler can now automatically provision Flagship apps when deploying Workers with Flagship bindings. +products: + - workers + - flagship +date: 2026-07-09 +--- + +import { WranglerConfig } from "~/components"; + +Wrangler automatic resource provisioning now supports Flagship bindings. Add a `flagship` binding without an `app_id`, and Wrangler can connect an existing Flagship app or create a new one during deployment. Wrangler writes the resulting `app_id` back to your configuration file. + + + +```jsonc +{ + "flagship": [ + { + "binding": "FLAGS", + }, + ], +} +``` + + + +For more information, refer to [automatic provisioning](/workers/wrangler/configuration/#automatic-provisioning) and [Flagship bindings](/flagship/binding/).