Skip to content

chore(deps): bump wrangler from 3.114.17 to 4.161.0 - #18

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/wrangler-4.161.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/wrangler-4.161.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown

Bumps wrangler from 3.114.17 to 4.161.0.

Release notes

Sourced from wrangler's releases.

wrangler@4.161.0

Minor Changes

  • #16840 8b2a363 Thanks @​jamesopstad! - Write source maps in Build Output with sources relative to each source map file

    This changes the experimental Build Output that wrangler build --experimental-cf-build-output and cf-wrangler build write. Their source maps were prepared as if for upload, with sources relative to the project root. For Workers that Wrangler does not bundle, leading ../ segments were also removed, which lost the location of some files. They now point from each source map's location in bundle/ to the original files, like the source maps the Vite plugin writes.

Patch Changes

  • #16833 5f539b5 Thanks @​jamesopstad! - Name cf commands and cloudflare.config.ts settings in remote bindings errors from cf-wrangler

    When cf runs development through the cf-wrangler delegate and remote bindings cannot be authenticated, the error now tells you to run cf auth whoami, cf auth logout and cf auth login instead of the Wrangler commands, and the Cloudflare Access hint names cf. The Flagship error for a binding whose app has not been created now names the binding's id setting instead of app_id, and suggests cf flagship apps create. wrangler dev still names Wrangler's commands and settings.

  • #16527 dc47e6d Thanks @​petebacondarwin! - Normalize relative redirect pathnames consistently across Pages and Workers assets

    Relative _redirects targets now use shared pathname normalization after placeholder replacement, keeping repeated separators within the site's path. Explicit external targets (including scheme-less URLs such as //example.com/path), query values and fragments retain their contents.

  • #16559 575d136 Thanks @​edmundhung! - Update @netlify/build-info to 11.3.1

  • #16838 3626ee8 Thanks @​jamesopstad! - Keep the remote bindings session when you remove the last remote binding

    When you removed the last remote binding while wrangler dev was running, Wrangler restarted the remote bindings session with credentials that ignored --profile and the account_id in your Wrangler config. So it could use a different account or ask you to choose one. Wrangler now keeps the existing session, and starts a new one with your current credentials when you add a remote binding again.

  • Updated dependencies [dc47e6d]:

wrangler@4.160.1

Patch Changes

wrangler@4.160.0

Minor Changes

  • #16760 cb9534f Thanks @​petebacondarwin! - Support forwarded Wrangler development server options in the experimental cf-wrangler delegate

    cf dev can now forward options such as --inspector-port 9229, --ip, --var, and --persist-to to the Wrangler development runtime. The delegate reuses Wrangler's dev option definitions and validation while retaining project config discovery, --mode environment selection, local development, and its .cloudflare/state default. Invalid option combinations produce a single-line usage error and exit code 2 before starting the server.

    Place server options that overlap cf's global options after --, for example cf dev -- --local --persist-to "custom state". Config and script overrides, whole-worker remote development, and Wrangler's global options remain unsupported.

  • #16739 6af492e Thanks @​GregBrimble! - Add custom Cloudflare API headers through CLOUDFLARE_API_HEADERS

    Set CLOUDFLARE_API_HEADERS to a JSON object such as {"X-Custom-Header":"value"} to add headers to Cloudflare API requests. Custom headers override existing unprotected request headers, body and transport headers are protected, and header values outside the diagnostic allowlist remain redacted regardless of log sanitization settings.

Patch Changes

  • #16810 cdc970b Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-10

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

... (truncated)

Commits
  • 1e688ba Version Packages (#16836)
  • 8b2a363 Write source maps in Build Output with sources relative to each source map ...
  • 575d136 [autoconfig] Support SolidStart 2 on cf (#16559)
  • 3626ee8 Remove CLOUDFLARE_CF_AUTH and require explicit auth for remote bindings ses...
  • 5f539b5 Name cf commands and settings in remote bindings errors (#16833)
  • 12a9105 [wrangler] Quiet E2E cleanup and preserve deployment failure output (#16832)
  • cc238b2 Version Packages (#16814)
  • d434f33 [miniflare] [wrangler] Parallelize the tests workerd's CI runs (#16823)
  • 5966749 [vitest-plugin] Support Container tests with cloudflare.config.ts (#16682)
  • 2674eef Version Packages (#16799)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) from 3.114.17 to 4.161.0.
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.161.0/packages/wrangler)

---
updated-dependencies:
- dependency-name: wrangler
  dependency-version: 4.161.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Hey - I've found 3 security issues

Security issues:

  • LGPL-3.0-or-later: Open-source license can require releasing the entire application source (link)
  • LGPL-3.0-or-later: Open-source license can require releasing the entire application source (link)
  • Apache-2.0 AND LGPL-3.0-or-later: Open-source license can require releasing the entire application source (link)
Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="package-lock.json" line_range="741-760" />
<code_context>

</code_context>
<issue_to_address>
**security (license/@img/sharp-libvips-linux-ppc64):** LGPL-3.0-or-later: Open-source license can require releasing the entire application source

This `LGPL-3.0-or-later` open-source license can impose strong copyleft or non-commercial obligations that may require releasing your full application source code or restrict commercial use, depending on how the code is used or distributed

*Source: trivy*
</issue_to_address>

### Comment 2
<location path="package-lock.json" line_range="761-774" />
<code_context>

</code_context>
<issue_to_address>
**security (license/@img/sharp-libvips-linux-riscv64):** LGPL-3.0-or-later: Open-source license can require releasing the entire application source

This `LGPL-3.0-or-later` open-source license can impose strong copyleft or non-commercial obligations that may require releasing your full application source code or restrict commercial use, depending on how the code is used or distributed

*Source: trivy*
</issue_to_address>

### Comment 3
<location path="package-lock.json" line_range="1106-1125" />
<code_context>

</code_context>
<issue_to_address>
**security (license/@img/sharp-win32-arm64):** Apache-2.0 AND LGPL-3.0-or-later: Open-source license can require releasing the entire application source

This `Apache-2.0 AND LGPL-3.0-or-later` open-source license can impose strong copyleft or non-commercial obligations that may require releasing your full application source code or restrict commercial use, depending on how the code is used or distributed

*Source: trivy*
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Comment thread package-lock.json
Comment on lines +741 to +760
"node_modules/@img/sharp-libvips-linux-ppc64": {
"version": "1.3.4",
"resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-ppc64/-/sharp-libvips-linux-ppc64-1.3.4.tgz",
"integrity": "sha512-Le6boB8Tai0Nis+gIxIpKx68UDVVIqdR8Tin5Yf1z2LJJQLDJvCDRqRu+jC2qCoD+eIomonmOwB4smBRxfVpYQ==",
"cpu": [
"ppc64"
],
"dev": true,
"libc": [
"glibc"
],
"license": "LGPL-3.0-or-later",
"optional": true,
"os": [
"linux"
],
"funding": {
"url": "https://opencollective.com/libvips"
}
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

security (license/@img/sharp-libvips-linux-ppc64): LGPL-3.0-or-later: Open-source license can require releasing the entire application source

This LGPL-3.0-or-later open-source license can impose strong copyleft or non-commercial obligations that may require releasing your full application source code or restrict commercial use, depending on how the code is used or distributed

Source: trivy

Comment thread package-lock.json
Comment on lines +761 to 774
"node_modules/@img/sharp-libvips-linux-riscv64": {
"version": "1.3.4",
"resolved": "https://registry.npmjs.org/@img/sharp-libvips-linux-riscv64/-/sharp-libvips-linux-riscv64-1.3.4.tgz",
"integrity": "sha512-aHkkIEHPRdQEegJN20MLmGtxYD9R2wQr3Cwpddnu5+YKMt6Uzax7S9h5gpZTo8wyrGuZSlfQ63OevL5mTyOC7Q==",
"cpu": [
"riscv64"
],
"dev": true,
"libc": [
"glibc"
],
"license": "LGPL-3.0-or-later",
"optional": true,
"os": [

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

security (license/@img/sharp-libvips-linux-riscv64): LGPL-3.0-or-later: Open-source license can require releasing the entire application source

This LGPL-3.0-or-later open-source license can impose strong copyleft or non-commercial obligations that may require releasing your full application source code or restrict commercial use, depending on how the code is used or distributed

Source: trivy

Comment thread package-lock.json
Comment on lines +1106 to 1125
"node_modules/@img/sharp-win32-arm64": {
"version": "0.35.5",
"resolved": "https://registry.npmjs.org/@img/sharp-win32-arm64/-/sharp-win32-arm64-0.35.5.tgz",
"integrity": "sha512-X4t7g+7ZA5DKblCBEXGjUqqemj4vczING/5viFwAL8h4N3qYeyjwdCvRLHi4EdOUI+2Z7UFlp1VM+p/AuEtm6Q==",
"cpu": [
"arm64"
],
"dev": true,
"license": "Apache-2.0 AND LGPL-3.0-or-later",
"optional": true,
"os": [
"win32"
],
"engines": {
"node": ">=20.9.0"
},
"funding": {
"url": "https://opencollective.com/libvips"
}
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

security (license/@img/sharp-win32-arm64): Apache-2.0 AND LGPL-3.0-or-later: Open-source license can require releasing the entire application source

This Apache-2.0 AND LGPL-3.0-or-later open-source license can impose strong copyleft or non-commercial obligations that may require releasing your full application source code or restrict commercial use, depending on how the code is used or distributed

Source: trivy

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants