Skip to content

Bump the wrangler-ecosystem group across 6 directories with 1 update - #1013

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/workers/audit-worker/wrangler-ecosystem-d24780b31e
Open

Bump the wrangler-ecosystem group across 6 directories with 1 update#1013
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/workers/audit-worker/wrangler-ecosystem-d24780b31e

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 15, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the wrangler-ecosystem group with 1 update in the /workers/audit-worker directory: wrangler.
Bumps the wrangler-ecosystem group with 1 update in the /workers/data-worker directory: wrangler.
Bumps the wrangler-ecosystem group with 1 update in the /workers/image-worker directory: wrangler.
Bumps the wrangler-ecosystem group with 1 update in the /workers/lists-worker directory: wrangler.
Bumps the wrangler-ecosystem group with 1 update in the /workers/pdf-worker directory: wrangler.
Bumps the wrangler-ecosystem group with 1 update in the /workers/user-worker directory: wrangler.

Updates wrangler from 4.127.1 to 4.131.1

Release notes

Sourced from wrangler's releases.

wrangler@4.131.1

Patch Changes

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Add a provisioning delay note when custom domain Preview URLs change

    Wrangler now explains that DNS and TLS certificate provisioning may continue after a deploy adds a custom domain or enables its Preview URLs. Stable redeploys don't repeat the note.

    This assumes that a request which matches the stored custom domain state doesn't restart provisioning. The client infers this from the API changeset and current domain record because this repository can't verify the backend behavior.

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Clarify production status labels for custom domain routes

    Wrangler now prefixes explicit custom domain production states with production: so they match Preview labels. The updated labels appear in deployed trigger output and WRANGLER_OUTPUT_FILE_PATH.

  • #15602 47d906f Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260910.1 ^5.20260911.1
    workerd 1.20260910.1 1.20260911.1

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Avoid replacement prompts for custom domains already on the Worker

    Wrangler now updates Preview settings without asking to replace a custom domain when that domain already belongs to the deployed Worker. It still asks before replacing domains attached to another Worker.

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Explain how to enable Preview URLs when a Preview deployment has none

    wrangler preview now shows URL shapes and configuration snippets for Workers.dev and custom domains. The custom domain snippet preserves every configured route, and the guidance distinguishes missing settings from disabled ones.

    This changes a private beta feature. The warning also makes clear that wrangler deploy publishes code from the current checkout.

  • Updated dependencies [47d906f, c2699bf]:

wrangler@4.131.0

Minor Changes

  • #15480 36aed7f Thanks @​skepticfx! - Add Durable Object-managed Containers to top-level container configuration

    Wrangler now accepts scheduling_policy: "durable_object" in the top-level containers array and creates its namespace-backed application after the Worker upload resolves the Durable Object namespace ID. The namespace ID is also the application ID, so repeated deploys idempotently ensure the same application without name-based lookup, modification, or a Containers rollout.

    Durable Object-managed entries accept class_name, scheduling_policy, an optional name, and an optional named images map. Scheduler-only fields are rejected. Each image provides either a local dockerfile or a digest-pinned managed-registry image. Wrangler builds or resolves each image, waits while Cloudflare prepares it for the Containers runtime, and uploads the resulting references with the Worker version for access through ctx.container.images and env.EXPERIMENTAL_CLOUDFLARE_CONTAINER_IMAGES. Local development support for these entries is deferred to a follow-up.

    Existing scheduler-backed entries and Durable Object migrations continue to work unchanged.

    With --containers-rollout=none, existing Workers retain their deployed Container metadata and image binding even when local containers is omitted or empty; local scheduler edits are also ignored. The upload stops if the deployed versions cannot be recovered. Existing Workers for Platforms dispatch scripts reject this flag before upload because their API does not expose enough metadata to preserve Container associations safely. First deployments can still skip Container preparation and rollout. Without this flag, removing managed Containers, including by omitting containers entirely, clears the experimental image binding even with keep_vars.

    versions deploy validates the selected versions before changing traffic and creates their Durable Object-managed applications only after deployment succeeds. Both deploy and versions deploy report partial completion if application creation fails afterward, with instructions to retry the same command.

... (truncated)

Commits

Updates wrangler from 4.127.1 to 4.131.1

Release notes

Sourced from wrangler's releases.

wrangler@4.131.1

Patch Changes

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Add a provisioning delay note when custom domain Preview URLs change

    Wrangler now explains that DNS and TLS certificate provisioning may continue after a deploy adds a custom domain or enables its Preview URLs. Stable redeploys don't repeat the note.

    This assumes that a request which matches the stored custom domain state doesn't restart provisioning. The client infers this from the API changeset and current domain record because this repository can't verify the backend behavior.

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Clarify production status labels for custom domain routes

    Wrangler now prefixes explicit custom domain production states with production: so they match Preview labels. The updated labels appear in deployed trigger output and WRANGLER_OUTPUT_FILE_PATH.

  • #15602 47d906f Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260910.1 ^5.20260911.1
    workerd 1.20260910.1 1.20260911.1

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Avoid replacement prompts for custom domains already on the Worker

    Wrangler now updates Preview settings without asking to replace a custom domain when that domain already belongs to the deployed Worker. It still asks before replacing domains attached to another Worker.

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Explain how to enable Preview URLs when a Preview deployment has none

    wrangler preview now shows URL shapes and configuration snippets for Workers.dev and custom domains. The custom domain snippet preserves every configured route, and the guidance distinguishes missing settings from disabled ones.

    This changes a private beta feature. The warning also makes clear that wrangler deploy publishes code from the current checkout.

  • Updated dependencies [47d906f, c2699bf]:

wrangler@4.131.0

Minor Changes

  • #15480 36aed7f Thanks @​skepticfx! - Add Durable Object-managed Containers to top-level container configuration

    Wrangler now accepts scheduling_policy: "durable_object" in the top-level containers array and creates its namespace-backed application after the Worker upload resolves the Durable Object namespace ID. The namespace ID is also the application ID, so repeated deploys idempotently ensure the same application without name-based lookup, modification, or a Containers rollout.

    Durable Object-managed entries accept class_name, scheduling_policy, an optional name, and an optional named images map. Scheduler-only fields are rejected. Each image provides either a local dockerfile or a digest-pinned managed-registry image. Wrangler builds or resolves each image, waits while Cloudflare prepares it for the Containers runtime, and uploads the resulting references with the Worker version for access through ctx.container.images and env.EXPERIMENTAL_CLOUDFLARE_CONTAINER_IMAGES. Local development support for these entries is deferred to a follow-up.

    Existing scheduler-backed entries and Durable Object migrations continue to work unchanged.

    With --containers-rollout=none, existing Workers retain their deployed Container metadata and image binding even when local containers is omitted or empty; local scheduler edits are also ignored. The upload stops if the deployed versions cannot be recovered. Existing Workers for Platforms dispatch scripts reject this flag before upload because their API does not expose enough metadata to preserve Container associations safely. First deployments can still skip Container preparation and rollout. Without this flag, removing managed Containers, including by omitting containers entirely, clears the experimental image binding even with keep_vars.

    versions deploy validates the selected versions before changing traffic and creates their Durable Object-managed applications only after deployment succeeds. Both deploy and versions deploy report partial completion if application creation fails afterward, with instructions to retry the same command.

... (truncated)

Commits

Updates wrangler from 4.127.1 to 4.131.1

Release notes

Sourced from wrangler's releases.

wrangler@4.131.1

Patch Changes

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Add a provisioning delay note when custom domain Preview URLs change

    Wrangler now explains that DNS and TLS certificate provisioning may continue after a deploy adds a custom domain or enables its Preview URLs. Stable redeploys don't repeat the note.

    This assumes that a request which matches the stored custom domain state doesn't restart provisioning. The client infers this from the API changeset and current domain record because this repository can't verify the backend behavior.

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Clarify production status labels for custom domain routes

    Wrangler now prefixes explicit custom domain production states with production: so they match Preview labels. The updated labels appear in deployed trigger output and WRANGLER_OUTPUT_FILE_PATH.

  • #15602 47d906f Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260910.1 ^5.20260911.1
    workerd 1.20260910.1 1.20260911.1

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Avoid replacement prompts for custom domains already on the Worker

    Wrangler now updates Preview settings without asking to replace a custom domain when that domain already belongs to the deployed Worker. It still asks before replacing domains attached to another Worker.

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Explain how to enable Preview URLs when a Preview deployment has none

    wrangler preview now shows URL shapes and configuration snippets for Workers.dev and custom domains. The custom domain snippet preserves every configured route, and the guidance distinguishes missing settings from disabled ones.

    This changes a private beta feature. The warning also makes clear that wrangler deploy publishes code from the current checkout.

  • Updated dependencies [47d906f, c2699bf]:

wrangler@4.131.0

Minor Changes

  • #15480 36aed7f Thanks @​skepticfx! - Add Durable Object-managed Containers to top-level container configuration

    Wrangler now accepts scheduling_policy: "durable_object" in the top-level containers array and creates its namespace-backed application after the Worker upload resolves the Durable Object namespace ID. The namespace ID is also the application ID, so repeated deploys idempotently ensure the same application without name-based lookup, modification, or a Containers rollout.

    Durable Object-managed entries accept class_name, scheduling_policy, an optional name, and an optional named images map. Scheduler-only fields are rejected. Each image provides either a local dockerfile or a digest-pinned managed-registry image. Wrangler builds or resolves each image, waits while Cloudflare prepares it for the Containers runtime, and uploads the resulting references with the Worker version for access through ctx.container.images and env.EXPERIMENTAL_CLOUDFLARE_CONTAINER_IMAGES. Local development support for these entries is deferred to a follow-up.

    Existing scheduler-backed entries and Durable Object migrations continue to work unchanged.

    With --containers-rollout=none, existing Workers retain their deployed Container metadata and image binding even when local containers is omitted or empty; local scheduler edits are also ignored. The upload stops if the deployed versions cannot be recovered. Existing Workers for Platforms dispatch scripts reject this flag before upload because their API does not expose enough metadata to preserve Container associations safely. First deployments can still skip Container preparation and rollout. Without this flag, removing managed Containers, including by omitting containers entirely, clears the experimental image binding even with keep_vars.

    versions deploy validates the selected versions before changing traffic and creates their Durable Object-managed applications only after deployment succeeds. Both deploy and versions deploy report partial completion if application creation fails afterward, with instructions to retry the same command.

... (truncated)

Commits

Updates wrangler from 4.127.1 to 4.131.1

Release notes

Sourced from wrangler's releases.

wrangler@4.131.1

Patch Changes

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Add a provisioning delay note when custom domain Preview URLs change

    Wrangler now explains that DNS and TLS certificate provisioning may continue after a deploy adds a custom domain or enables its Preview URLs. Stable redeploys don't repeat the note.

    This assumes that a request which matches the stored custom domain state doesn't restart provisioning. The client infers this from the API changeset and current domain record because this repository can't verify the backend behavior.

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Clarify production status labels for custom domain routes

    Wrangler now prefixes explicit custom domain production states with production: so they match Preview labels. The updated labels appear in deployed trigger output and WRANGLER_OUTPUT_FILE_PATH.

  • #15602 47d906f Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260910.1 ^5.20260911.1
    workerd 1.20260910.1 1.20260911.1

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Avoid replacement prompts for custom domains already on the Worker

    Wrangler now updates Preview settings without asking to replace a custom domain when that domain already belongs to the deployed Worker. It still asks before replacing domains attached to another Worker.

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Explain how to enable Preview URLs when a Preview deployment has none

    wrangler preview now shows URL shapes and configuration snippets for Workers.dev and custom domains. The custom domain snippet preserves every configured route, and the guidance distinguishes missing settings from disabled ones.

    This changes a private beta feature. The warning also makes clear that wrangler deploy publishes code from the current checkout.

  • Updated dependencies [47d906f, c2699bf]:

wrangler@4.131.0

Minor Changes

  • #15480 36aed7f Thanks @​skepticfx! - Add Durable Object-managed Containers to top-level container configuration

    Wrangler now accepts scheduling_policy: "durable_object" in the top-level containers array and creates its namespace-backed application after the Worker upload resolves the Durable Object namespace ID. The namespace ID is also the application ID, so repeated deploys idempotently ensure the same application without name-based lookup, modification, or a Containers rollout.

    Durable Object-managed entries accept class_name, scheduling_policy, an optional name, and an optional named images map. Scheduler-only fields are rejected. Each image provides either a local dockerfile or a digest-pinned managed-registry image. Wrangler builds or resolves each image, waits while Cloudflare prepares it for the Containers runtime, and uploads the resulting references with the Worker version for access through ctx.container.images and env.EXPERIMENTAL_CLOUDFLARE_CONTAINER_IMAGES. Local development support for these entries is deferred to a follow-up.

    Existing scheduler-backed entries and Durable Object migrations continue to work unchanged.

    With --containers-rollout=none, existing Workers retain their deployed Container metadata and image binding even when local containers is omitted or empty; local scheduler edits are also ignored. The upload stops if the deployed versions cannot be recovered. Existing Workers for Platforms dispatch scripts reject this flag before upload because their API does not expose enough metadata to preserve Container associations safely. First deployments can still skip Container preparation and rollout. Without this flag, removing managed Containers, including by omitting containers entirely, clears the experimental image binding even with keep_vars.

    versions deploy validates the selected versions before changing traffic and creates their Durable Object-managed applications only after deployment succeeds. Both deploy and versions deploy report partial completion if application creation fails afterward, with instructions to retry the same command.

... (truncated)

Commits

Updates wrangler from 4.127.1 to 4.131.1

Release notes

Sourced from wrangler's releases.

wrangler@4.131.1

Patch Changes

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Add a provisioning delay note when custom domain Preview URLs change

    Wrangler now explains that DNS and TLS certificate provisioning may continue after a deploy adds a custom domain or enables its Preview URLs. Stable redeploys don't repeat the note.

    This assumes that a request which matches the stored custom domain state doesn't restart provisioning. The client infers this from the API changeset and current domain record because this repository can't verify the backend behavior.

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Clarify production status labels for custom domain routes

    Wrangler now prefixes explicit custom domain production states with production: so they match Preview labels. The updated labels appear in deployed trigger output and WRANGLER_OUTPUT_FILE_PATH.

  • #15602 47d906f Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260910.1 ^5.20260911.1
    workerd 1.20260910.1 1.20260911.1

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Avoid replacement prompts for custom domains already on the Worker

    Wrangler now updates Preview settings without asking to replace a custom domain when that domain already belongs to the deployed Worker. It still asks before replacing domains attached to another Worker.

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Explain how to enable Preview URLs when a Preview deployment has none

    wrangler preview now shows URL shapes and configuration snippets for Workers.dev and custom domains. The custom domain snippet preserves every configured route, and the guidance distinguishes missing settings from disabled ones.

    This changes a private beta feature. The warning also makes clear that wrangler deploy publishes code from the current checkout.

  • Updated dependencies [47d906f, c2699bf]:

wrangler@4.131.0

Minor Changes

  • #15480 36aed7f Thanks @​skepticfx! - Add Durable Object-managed Containers to top-level container configuration

    Wrangler now accepts scheduling_policy: "durable_object" in the top-level containers array and creates its namespace-backed application after the Worker upload resolves the Durable Object namespace ID. The namespace ID is also the application ID, so repeated deploys idempotently ensure the same application without name-based lookup, modification, or a Containers rollout.

    Durable Object-managed entries accept class_name, scheduling_policy, an optional name, and an optional named images map. Scheduler-only fields are rejected. Each image provides either a local dockerfile or a digest-pinned managed-registry image. Wrangler builds or resolves each image, waits while Cloudflare prepares it for the Containers runtime, and uploads the resulting references with the Worker version for access through ctx.container.images and env.EXPERIMENTAL_CLOUDFLARE_CONTAINER_IMAGES. Local development support for these entries is deferred to a follow-up.

    Existing scheduler-backed entries and Durable Object migrations continue to work unchanged.

    With --containers-rollout=none, existing Workers retain their deployed Container metadata and image binding even when local containers is omitted or empty; local scheduler edits are also ignored. The upload stops if the deployed versions cannot be recovered. Existing Workers for Platforms dispatch scripts reject this flag before upload because their API does not expose enough metadata to preserve Container associations safely. First deployments can still skip Container preparation and rollout. Without this flag, removing managed Containers, including by omitting containers entirely, clears the experimental image binding even with keep_vars.

    versions deploy validates the selected versions before changing traffic and creates their Durable Object-managed applications only after deployment succeeds. Both deploy and versions deploy report partial completion if application creation fails afterward, with instructions to retry the same command.

... (truncated)

Commits

Updates wrangler from 4.127.1 to 4.131.1

Release notes

Sourced from wrangler's releases.

wrangler@4.131.1

Patch Changes

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Add a provisioning delay note when custom domain Preview URLs change

    Wrangler now explains that DNS and TLS certificate provisioning may continue after a deploy adds a custom domain or enables its Preview URLs. Stable redeploys don't repeat the note.

    This assumes that a request which matches the stored custom domain state doesn't restart provisioning. The client infers this from the API changeset and current domain record because this repository can't verify the backend behavior.

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Clarify production status labels for custom domain routes

    Wrangler now prefixes explicit custom domain production states with production: so they match Preview labels. The updated labels appear in deployed trigger output and WRANGLER_OUTPUT_FILE_PATH.

  • #15602 47d906f Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260910.1 ^5.20260911.1
    workerd 1.20260910.1 1.20260911.1

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Avoid replacement prompts for custom domains already on the Worker

    Wrangler now updates Preview settings without asking to replace a custom domain when that domain already belongs to the deployed Worker. It still asks before replacing domains attached to another Worker.

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Explain how to enable Preview URLs when a Preview deployment has none

    wrangler preview now shows URL shapes and configuration snippets for Workers.dev and custom domains. The custom domain snippet preserves every configured route, and the guidance distinguishes missing settings from disabled ones.

    This changes a private beta feature. The warning also makes clear that wrangler deploy publishes code from the current checkout.

  • Updated dependencies [47d906f, c2699bf]:

wrangler@4.131.0

Minor Changes

  • #15480 36aed7f Thanks @​skepticfx! - Add Durable Object-managed Containers to top-level container configuration

    Wrangler now accepts scheduling_policy: "durable_object" in the top-level containers array and creates its namespace-backed application after the Worker upload resolves the Durable Object namespace ID. The namespace ID is also the application ID, so repeated deploys idempotently ensure the same application without name-based lookup, modification, or a Containers rollout.

    Durable Object-managed entries accept class_name, scheduling_policy, an optional name, and an optional named images map. Scheduler-only fields are rejected. Each image provides either a local dockerfile or a digest-pinned managed-registry image. Wrangler builds or resolves each image, waits while Cloudflare prepares it for the Containers runtime, and uploads the resulting references with the Worker version for access through ctx.container.images and env.EXPERIMENTAL_CLOUDFLARE_CONTAINER_IMAGES. Local development support for these entries is deferred to a follow-up.

    Existing scheduler-backed entries and Durable Object migrations continue to work unchanged.

    With --containers-rollout=none, existing Workers retain their deployed Container metadata and image binding even when local containers is omitted or empty; local scheduler edits are also ignored. The upload stops if the deployed versions cannot be recovered. Existing Workers for Platforms dispatch scripts reject this flag before upload because their API does not expose enough metadata to preserve Container associations safely. First deployments can still skip Container preparation and rollout. Without this flag, removing managed Containers, including by omitting containers entirely, clears the experimental image binding even with keep_vars.

    versions deploy validates the selected versions before changing traffic and creates their Durable Object-managed applications only after deployment succeeds. Both deploy and versions deploy report partial completion if application creation fails afterward, with instructions to retry the same command.

... (truncated)

Commits

Updates wrangler from 4.127.1 to 4.131.1

Release notes

Sourced from wrangler's releases.

wrangler@4.131.1

Patch Changes

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Add a provisioning delay note when custom domain Preview URLs change

    Wrangler now explains that DNS and TLS certificate provisioning may continue after a deploy adds a custom domain or enables its Preview URLs. Stable redeploys don't repeat the note.

    This assumes that a request which matches the stored custom domain state doesn't restart provisioning. The client infers this from the API changeset and current domain record because this repository can't verify the backend behavior.

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Clarify production status labels for custom domain routes

    Wrangler now prefixes explicit custom domain production states with production: so they match Preview labels. The updated labels appear in deployed trigger output and WRANGLER_OUTPUT_FILE_PATH.

  • #15602 47d906f Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260910.1 ^5.20260911.1
    workerd 1.20260910.1 1.20260911.1

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Avoid replacement prompts for custom domains already on the Worker

    Wrangler now updates Preview settings without asking to replace a custom domain when that domain already belongs to the deployed Worker. It still asks before replacing domains attached to another Worker.

  • #15592 945aaa3 Thanks @​WillTaylorDev! - Explain how to enable Preview URLs when a Preview deployment has none

    wrangler preview now shows URL shapes and configuration snippets for Workers.dev and custom domains. The custom domain snippet preserves every configured route, and the guidance distinguishes missing settings from disabled ones.

    This changes a private beta feature. The warning also makes clear that wrangler deploy publishes code from the current checkout.

  • Updated dependencies [47d906f, c2699bf]:

wrangler@4.131.0

Minor Changes

@dependabot
Bump the wrangler-ecosystem group across 6 directories with 1 update
7474404 
Bumps the wrangler-ecosystem group with 1 update in the /workers/audit-worker directory: [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler).
Bumps the wrangler-ecosystem group with 1 update in the /workers/data-worker directory: [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler).
Bumps the wrangler-ecosystem group with 1 update in the /workers/image-worker directory: [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler).
Bumps the wrangler-ecosystem group with 1 update in the /workers/lists-worker directory: [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler).
Bumps the wrangler-ecosystem group with 1 update in the /workers/pdf-worker directory: [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler).
Bumps the wrangler-ecosystem group with 1 update in the /workers/user-worker directory: [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler).


Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

Updates `wrangler` from 4.127.1 to 4.131.1
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.131.1/packages/wrangler)

---
updated-dependencies:
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
- dependency-name: wrangler
  dependency-version: 4.131.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: wrangler-ecosystem
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Sep 15, 2026
Copilot AI lite review requested due to automatic review settings September 15, 2026 07:35
@dependabot dependabot Bot mentioned this pull request Sep 15, 2026
Closed
@socket-security

socket-security Bot commented Sep 15, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Addedwrangler@​4.131.1981009296100

View full report

Copilot AI reviewed Sep 15, 2026
View reviewed changes

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No unresolved review comments; changes are limited to dependency and lockfile updates.

Pull request overview

Updates Wrangler from 4.127.1 to 4.131.1 across six worker projects.

Changes:

  • Bumps Wrangler dependency versions.
  • Refreshes lockfiles and related Cloudflare runtime dependencies.
File summaries
File Summary
workers/user-worker/package.json Updates Wrangler.
workers/user-worker/package-lock.json Refreshes locked dependencies.
workers/pdf-worker/package.json Updates Wrangler.
workers/pdf-worker/package-lock.json Refreshes locked dependencies.
workers/lists-worker/package.json Updates Wrangler.
workers/lists-worker/package-lock.json Refreshes locked dependencies.
workers/image-worker/package.json Updates Wrangler.
workers/image-worker/package-lock.json Refreshes locked dependencies.
workers/data-worker/package.json Updates Wrangler.
workers/data-worker/package-lock.json Refreshes locked dependencies.
workers/audit-worker/package.json Updates Wrangler.
Review details

Files not reviewed (6)

  • workers/audit-worker/package-lock.json: Generated file
  • workers/data-worker/package-lock.json: Generated file
  • workers/image-worker/package-lock.json: Generated file
  • workers/lists-worker/package-lock.json: Generated file
  • workers/pdf-worker/package-lock.json: Generated file
  • workers/user-worker/package-lock.json: Generated file
  • Files reviewed: 6/12 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot
Copilot review effort, defaults to Lite
Applies to this pull request for everyone.Learn more about Copilot code review.
Copilot left review comments

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant