Repository navigation
chore(deps): update dependency wrangler to v4.163.0 - #64
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
renovate
Bot
force-pushed
the
renovate/wrangler-4.x
branch
from
November 16, 2026 18:34
bec991b to
e5315ec
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.161.0→4.163.0Release Notes
cloudflare/workers-sdk (wrangler)
v4.163.0Compare Source
Minor Changes
#16917
d36b39dThanks @jamesopstad! - Write Build Output to.cloudflare/output/v1/and record the producervite buildand the experimentalwrangler build --experimental-cf-build-outputnow write Build Output v1, with account settings nested undersettingsin the rootconfig.json. They also record themselves as theproducer, so readers can name the tool that wrote the output in error messages. Previews from Build Output read the account settings from their new location.#16246
349fc4eThanks @leostera! - Start local Workflows from Artifacts eventsDeclare Artifacts events on
exports.workflow({ name, events })incloudflare.config.tsto start the owning Workflow locally incf, Vite, and Workers Vitest. Wrangler configurations continue to usetriggers.events. Native config conversion derives those targets from the Workflow export, andcf migrateattaches existing event subscriptions to their matching Workflow exports.Local Artifacts namespaces publish the documented
cf.artifacts.*messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions.Patch Changes
#16803
b219078Thanks @petebacondarwin! - Run experimental cf projects with their installed Vite or Vite+ commandscf dev,cf build, and deployments that build your project can use Vite or Vite+ even when no framework command is detected. This removes the need for the internalcf-vitedelegate and supports dependencies declared and hoisted at the root of a configured workspace. A workspace application using a custom-named Vite config should declare@cloudflare/vite-pluginin its own manifest, or addviteorvite-plusas a dependency or dev dependency to identify its tooling; this keeps shared root tools from selecting Vite for non-Vite siblings. Configs passed later via--configare evaluated by Vite when the command runs. Existing framework commands keep their priority. Consumers resolve bare executables using the detectednodeModulesPathsin order, adding.binto each directory. Lookup stops at the validated workspace root; standalone applications use only their ownnode_modules/.bin.Project inspection can recognize an existing Cloudflare configuration before dependencies are installed. Running a command provides guidance when the required tools are missing or the plugin version does not support cf profiles (
>=2.0.0-beta.v.13 <3). Vite evaluates the project configuration when the command runs, including dynamic configs and custom config files. Repair guidance uses the project’s detected package manager. Automatic setup asks users to convert CommonJS.cjsand.ctsVite configs to ESM imports and exports in.mjsor.mtsbefore adding the ESM-only Cloudflare plugin. Native builds also work with the Windows shell. Pages migration safeguards, unsupported-framework setup checks, and Wrangler command selection retain their existing behavior.#16944
db3c071Thanks @danlapid! - Stopwrangler devfrom missing config file changes made soon after a reloadwrangler devreplaced its config file watcher on every reload without waiting for the new one to start, so a change saved in that gap was never applied. It now keeps one watcher while the set of watched files is unchanged, and reports a config as applied only once its files are being watched. A second change saved within 50 ms of the previous one is no longer dropped either.#16920
81e56ddThanks @benbuzbee! - Use the effectivemax_instancesvalue when choosing the default container rollout stepsWhen
max_instanceswas omitted, Wrangler deployed 20 instances but chose rollout steps as if there were 0 instances, so the rollout used a single 100% step. Wrangler now uses[10, 100]for omittedmax_instances, while still using a single 100% step whenmax_instancesis 0 or 1.#16946
e97c9f8Thanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-16Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16946
e97c9f8Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#16874
4335eacThanks @petebacondarwin! - Avoid redundant OAuth refreshes after a sibling process updates credentialsCheck access-token expiry and select the refresh token from the same fresh credential snapshot. When a sibling has already saved a valid access token, reuse it without another exchange or write. This prevents an unnecessary rotation that can let an older response overwrite a newer refresh token.
#16917
d36b39dThanks @jamesopstad! - Detect Cloudflare Build Output of any version before deployingwrangler deploy,wrangler versions uploadandwrangler previewrefuse to run in a project that has Cloudflare Build Output, because that output belongs tocf. Detection now looks for any.cloudflare/output/v<N>/directory rather than only the root config of the current version, so output left by an older or newercfis still caught.Updated dependencies [
e97c9f8,e97c9f8,349fc4e,0bf81ac]:v4.162.0Compare Source
Minor Changes
#16735
f005593Thanks @leostera! - Use the local simulator for Artifacts bindings that omitremoteBehavior change: Artifacts bindings now default to the local simulator during development, like KV, R2 and D1. Previously, an omitted
remotein Wrangler and the Vite plugin used the deployed Artifacts resource. If you want deployed repos inwrangler devorvite dev, set"remote": trueon the binding (dev: { remote: true }incloudflare.config.ts). Artifacts is in beta, so this ships as a minor release.While
remoteis omitted,wrangler dev,getPlatformProxy()and the Vite plugin warn when remote bindings are enabled, once for each binding rather than on every config reload: "Artifacts binding REPOS uses the local simulator by default. Setremote: trueto use deployed repos, orremote: falseto silence this warning." Workers Vitest andwrangler dev --localalready used the simulator, so they don't warn. Local Artifacts needs no Cloudflare credentials, but requires Git 2.32 or newer on the host.#16749
032f8c2Thanks @vaishnav-mk! - Reject settings on aworkflowsbinding to a Workflow declared inexportsA
workflowsbinding can still bind a Workflow that the Worker declares inexports, but it can no longer setlimits,concurrency,schedules,default_retention, orjurisdictionfor it. Set them on the export instead. Previously the binding and the export could both set them as long as they agreed, so configurations that set them on the binding now stop with an error that says which setting to move.#16749
032f8c2Thanks @vaishnav-mk! - Upload Workflow export settings with the Workerwrangler deployandwrangler versions uploadnow include the settings of eachworkflowexport (limits,concurrency,schedules,default_retention, andjurisdiction) in the upload, instead of sending only its type and name. Uploads of a Worker withworkflowexports also send aCloudflare-Workers-Script-Api-Dateheader, which lets the Workers API provision Workflow exports from these settings as part of the upload.wrangler deployandwrangler triggers deploystill create or update each Workflow through the Workflows API afterwards, as before.If provisioning a scheduled Workflow fails because the account is on the free plan,
wrangler deploynow explains that scheduled Workflows require a paid Workers plan.Patch Changes
#16849
3cea40bThanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-12Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16886
63eb6daThanks @dependabot! - UpdateDEFAULT_COMPAT_DATEto 2026-11-13Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16849
3cea40bThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#16886
63eb6daThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#16864
3b1b408Thanks @MattieTK! - Fix packages with nestedpackage.jsonfiles missing from deploy metadataPackages such as
hono,stripeand@modelcontextprotocol/sdkwere silently omitted from the package dependency metadata reported duringwrangler deployandwrangler versions upload. These packages are now included with their installed versions. Autoconfig and codemods also detect their installed versions correctly.#16862
c889551Thanks @petebacondarwin! - Fix requests hanging when a local Worker reload finishes before an inflight request failsWrangler now immediately processes retriable requests when the replacement Worker is already ready. Previously, these requests could remain queued until another request arrived, particularly on Windows where connection failures can take longer to report.
Updated dependencies [
f005593,61eacca,856842e,856842e,3cea40b,63eb6da,3cea40b,63eb6da]:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.