Skip to content

Conversation

@workers-devprod
Copy link
Contributor

@workers-devprod workers-devprod commented Nov 26, 2025

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@cloudflare/[email protected]

Minor Changes

  • #11408 f29e699 Thanks @ascorbic! - Support zero-config operation

    If the Vite plugin is used in a project without an existing Wrangler config file, it should be able to operate in "zero-config" mode by generating a default Wrangler configuration for an assets-only worker.

  • #11417 2ca70b1 Thanks @jamesopstad! - Register named entrypoints with the dev registry.

    This enables binding to named entrypoints defined in a vite dev session from another vite dev or wrangler dev session running locally.

Patch Changes

[email protected]

Minor Changes

  • #11416 abe49d8 Thanks @dario-piotrowicz! - Remove the wrangler deploy's --x-remote-diff-check experimental flag

    The remote diffing feature has been enabled by default for a while and its functionality is stable, as a result the experimental flag (only available for option-out of the feature right now) has been removed.

  • #11408 f29e699 Thanks @ascorbic! - Export unstable helpers useful for generating wrangler config

  • #11375 9a1de61 Thanks @penalosa! - Support Tanstack in autoconfig

  • #11009 e4ddbc2 Thanks @dario-piotrowicz! - Allow users to provide an account_id as part of the WorkerConfigObject they pass to maybeStartOrUpdateRemoteProxySession

  • #11330 5a873bb Thanks @dario-piotrowicz! - Support Angular projects in autoconfig

  • #11449 e7b690b Thanks @penalosa! - Delegate generation of HTTPS certificates to Miniflare

  • #11448 2b4813b Thanks @edmundhung! - Bumps esbuild version to 0.27.0

  • #11335 c47ad11 Thanks @dario-piotrowicz! - Support internal-only undocumented cross_account_grant service binding property

  • #11346 a977701 Thanks @penalosa! - We're soon going to make backend changes that mean that wrangler dev --remote sessions will no longer have an associated inspector connection. In advance of these backend changes, we've enabled a new wrangler tail-based logging strategy for wrangler dev --remote. For now, you can revert to the previous logging strategy with wrangler dev --remote --no-x-tail-logs, but in future it will not be possible to revert.

    The impact of this will be that logs that were previously available via devtools will now be provided directly to the Wrangler console and it will no longer be possible to interact with the remote Worker via the devtools console.

Patch Changes

  • #11397 b154de2 Thanks @vicb! - Use more workerd native modules

    Node modules punycode, trace_events, cluster, wasi, and domains will be used when enabled
    via a compatibility flag or by default when the compatibility date is greater or equal to 2025-12-04.

  • #11452 76f0540 Thanks @penalosa! - Remove uses eval() from the Wrangler bundle

  • #11389 2342d2f Thanks @dario-piotrowicz! - Improve the wrangler deploy flow to also check for potential overrides of secrets.

    Now when you run wrangler deploy Wrangler will check the remote secrets for your workers for conflicts with the names of the bindings you're about to deploy. If there are conflicts, Wrangler will warn you and ask you for your permission before proceeding.

  • #11284 695fa25 Thanks @dom96! - Removes duplicate module warnings when vendoring Python packages

  • #11249 504e258 Thanks @dario-piotrowicz! - fix: Generalize autoconfig wording

    Generalize the autoconfig wording so that when it doesn't specifically mention "deployment" (since it can be run via wrangler setup or the autoconfig programmatic API)

  • #11455 d25f7e2 Thanks @dario-piotrowicz! - Fix autoconfig using absolute paths for static projects

    Running the experimental autoconfig logic through wrangler setup and wrangler deploy --x-autoconfig on a static project results in absolute paths being used, this is incorrect, especially when such paths are being included in the generated wrangler.jsonc, the changes here fix the autoconfig logic to instead use paths relative to the project's root instead.

    For example given a project located in /Users/usr/projects/sites/my-static-site, before:

    // wrangler.jsonc at /Users/usr/projects/sites/my-static-site
      {
        "$schema": "node_modules/wrangler/config-schema.json",
        "name": "static",
        "compatibility_date": "2025-11-27",
        "observability": {
          "enabled": true
        },
        "assets": {
          "directory": "/Users/usr/projects/sites/my-static-site/public"
        }
      }

    and after:

    // wrangler.jsonc at /Users/usr/projects/sites/my-static-site
      {
        "$schema": "node_modules/wrangler/config-schema.json",
        "name": "static",
        "compatibility_date": "2025-11-27",
        "observability": {
          "enabled": true
        },
        "assets": {
          "directory": "public"
        }
      }
  • #11383 1d685cb Thanks @dario-piotrowicz! - Fix: ensure that when a remote proxy session creation fails a hard error is surfaced to the user (both in wrangler dev and in the programmatic API).

    When using remote bindings, either with wrangler dev or via startRemoteProxySession/maybeStartOrUpdateRemoteProxySession the remote proxy session necessary to connect to the remote resources can fail to be created, this might happen if for example you try to set a binding with some invalid values such as:

    MY_R2: {
    	type: "r2_bucket",
    	bucket_name: "non-existent", // No bucket called "non-existent" exists
    	remote: true,
    },

    Before this could go undetected and cause unwanted behaviors such as requests handling hanging indefinitely, now wrangler will instead crash (or throw a hard error ion the programmatic API), clearly indicating that something went wrong during the remote session's creation.

  • #11366 edf896d Thanks @ascorbic! - Use correctly-formatted names when displayed detected framework details

  • #11461 9eaa9e2 Thanks @dario-piotrowicz! - Update the structure of the configure method of autoconfig frameworks

    Update the signature of the configure function of autoconfig frameworks (AutoconfigDetails#Framework), before they would return a RawConfig object to use to update the project's wrangler config file, now they return an object that includes the RawConfig and that can potentially also hold additional data relevant to the configuration.

  • Updated dependencies [2b4813b, b154de2, 5ee3780, 6e63b57, 71ab562, 5e937c1]:

[email protected]

Patch Changes

[email protected]

Patch Changes

  • #11448 2b4813b Thanks @edmundhung! - Builds package with esbuild v0.27.0

  • #11419 5ee3780 Thanks @dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251125.0 1.20251126.0
  • #11444 6e63b57 Thanks @dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251126.0 1.20251127.0
  • #11457 71ab562 Thanks @dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251127.0 1.20251128.0
  • #11391 5e937c1 Thanks @pmiguel! - Set minimum KV Cache TTL in Miniflare to 30 seconds

@cloudflare/[email protected]

Patch Changes

@cloudflare/[email protected]

Patch Changes

  • #11397 b154de2 Thanks @vicb! - Use more workerd native modules

    Node modules punycode, trace_events, cluster, wasi, and domains will be used when enabled
    via a compatibility flag or by default when the compatibility date is greater or equal to 2025-12-04.

@cloudflare/[email protected]

Patch Changes

@cloudflare/[email protected]

Minor Changes

@cloudflare/[email protected]

Patch Changes

@cloudflare/[email protected]

Patch Changes

@cloudflare/[email protected]

Patch Changes

@cloudflare/[email protected]

Patch Changes

@cloudflare/[email protected]

Patch Changes

@workers-devprod workers-devprod requested review from a team as code owners November 26, 2025 15:19
@pkg-pr-new
Copy link

pkg-pr-new bot commented Nov 26, 2025

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@11427

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@11427

miniflare

npm i https://pkg.pr.new/miniflare@11427

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@11427

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@11427

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@11427

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@11427

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@11427

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@11427

wrangler

npm i https://pkg.pr.new/wrangler@11427

commit: 569246d

@workers-devprod workers-devprod force-pushed the changeset-release/main branch 27 times, most recently from 058bfa5 to 6741789 Compare November 28, 2025 12:27
@workers-devprod workers-devprod force-pushed the changeset-release/main branch 10 times, most recently from d11baf1 to 70fc202 Compare November 28, 2025 23:22
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.

1 participant