From 28bf23861ec601d2fea77c1d32bf411abd8d4f45 Mon Sep 17 00:00:00 2001 From: Christian Sparks Date: Mon, 3 Feb 2025 14:22:49 -0600 Subject: [PATCH 1/3] Add WCI WRANGLER_CI_OVERRIDE_NAME documentation --- src/content/docs/workers/ci-cd/builds/troubleshoot.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx b/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx index 4c1bc495026ef51..b5ffcef14e8f8ba 100644 --- a/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx +++ b/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx @@ -26,6 +26,8 @@ The build system uses the `name` argument in the wrangler.toml to determine whic This does not apply to [Wrangler Environments](/workers/wrangler/environments/) if the Worker name before the `-` suffix matches the name in wrangler.toml. For example, a Worker named `my-worker-staging` on the dashboard can be deployed from a repository that contains a wrangler.toml with the arguments `name = my-worker` and `[env.staging]` using the deploy command `npx wrangler deploy --env staging`. + +Additionally, on Wrangler versions greater than 3.xx, Workers Builds will automatically override the name to match the worker it is connected to using the `WRANGLER_CI_OVERRIDE_NAME` environment variable. ::: ### Missing wrangler.toml @@ -42,7 +44,7 @@ If you see this error, the wrangler.toml likely has an `account_id` for a differ ### Stale API token -` Failed: The build token selected for this build has been deleted or rolled and cannot be used for this build. Please update your build token in the Worker Builds settings and retry the build.` +` Failed: The build token selected for this build has been deleted or rolled and cannot be used for this build. Please update your build token in the Worker Builds settings and retry the build.` The API Token dropdown in Build Configuration settings may show stale tokens that were edited, deleted, or rolled. If you encounter an error due to a stale token, create a new API Token and select it for the build. From cbac117844483fb8710020bc1b8ca64b66b4e57d Mon Sep 17 00:00:00 2001 From: ToriLindsay Date: Wed, 16 Apr 2025 11:32:29 +0100 Subject: [PATCH 2/3] Update src/content/docs/workers/ci-cd/builds/troubleshoot.mdx Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> --- src/content/docs/workers/ci-cd/builds/troubleshoot.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx b/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx index b5ffcef14e8f8ba..cb01e14ffc3b25e 100644 --- a/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx +++ b/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx @@ -27,7 +27,7 @@ This does not apply to [Wrangler Environments](/workers/wrangler/environments/) For example, a Worker named `my-worker-staging` on the dashboard can be deployed from a repository that contains a wrangler.toml with the arguments `name = my-worker` and `[env.staging]` using the deploy command `npx wrangler deploy --env staging`. -Additionally, on Wrangler versions greater than 3.xx, Workers Builds will automatically override the name to match the worker it is connected to using the `WRANGLER_CI_OVERRIDE_NAME` environment variable. +Additionally, on Wrangler versions greater than 3.xx, Workers Builds will automatically override the name to match the Worker it is connected to using the `WRANGLER_CI_OVERRIDE_NAME` environment variable. ::: ### Missing wrangler.toml From 84ae76f93fdf937e452adc9af04ccca45c9d12fc Mon Sep 17 00:00:00 2001 From: Kody Jackson Date: Mon, 19 May 2025 17:20:00 -0500 Subject: [PATCH 3/3] Update src/content/docs/workers/ci-cd/builds/troubleshoot.mdx Co-authored-by: ToriLindsay --- src/content/docs/workers/ci-cd/builds/troubleshoot.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx b/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx index cb01e14ffc3b25e..249a484da2bb404 100644 --- a/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx +++ b/src/content/docs/workers/ci-cd/builds/troubleshoot.mdx @@ -27,7 +27,7 @@ This does not apply to [Wrangler Environments](/workers/wrangler/environments/) For example, a Worker named `my-worker-staging` on the dashboard can be deployed from a repository that contains a wrangler.toml with the arguments `name = my-worker` and `[env.staging]` using the deploy command `npx wrangler deploy --env staging`. -Additionally, on Wrangler versions greater than 3.xx, Workers Builds will automatically override the name to match the Worker it is connected to using the `WRANGLER_CI_OVERRIDE_NAME` environment variable. +On Wrangler v3 and up, Workers Builds automatically matches the name of the connected Worker by overriding it with the `WRANGLER_CI_OVERRIDE_NAME` environment variable. ::: ### Missing wrangler.toml