Skip to content

Version Packages - #15555

Merged
petebacondarwin merged 1 commit into
mainfrom
changeset-release/main
Sep 8, 2026
Merged

petebacondarwin merged 1 commit into
mainfrom
changeset-release/main

Conversation

@workers-devprod

@workers-devprod workers-devprod commented Sep 7, 2026 •

Copy link
Copy Markdown
Contributor

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/config@0.11.0

Minor Changes

  • #15511 9c60d14 Thanks @jamesopstad! - Enable referencing Worker configs directly in cross-Worker bindings

    defineWorker and defineSettings now return ordinary config objects, functions, or promises. Cross-Worker bindings can use a defineWorker result as their worker, preserving type inference while resolving and parsing the referenced config only once.

miniflare@5.20260908.0-alpha

Minor Changes

  • #15268 bcebf08 Thanks @akshitsinha! - Simulate Flagship bindings locally

    Flagship bindings can now evaluate flags against a persisted local store instead of requiring a remote app. Miniflare also exposes an admin API for populating and managing that store in development tools and tests, while bindings configured for remote access continue to proxy to Flagship.

Patch Changes

  • #15560 edb3631 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @cloudflare/workers-types ^5.20260907.1 ^5.20260908.1
    workerd 1.20260907.1 1.20260908.1

@cloudflare/workers-utils@0.37.0

Minor Changes

  • #15470 a849e0d Thanks @edmundhung! - Move named tunnel resolution into workers-utils

    Wrangler continues to expose the same behavior while delegating the implementation to the shared utility.

wrangler@4.130.0

Minor Changes

  • #14372 dbf6aad Thanks @ichernetsky-cf! - Add containers[].observability support to wrangler deploy

    Wrangler now accepts container-specific observability settings via containers[].observability, including application-level targeting fields for Containers. Root observability continues to work as a fallback when a container does not define its own observability settings.

    wrangler deploy now preserves legacy configuration.observability for existing container apps that still use rollout-based observability, while using top-level application observability for new or already-migrated apps.

    Existing application diffs are now normalized even when stored resource limits cannot be mapped to a named instance type. API-only metadata and equivalent managed-registry image names no longer appear as edits or affect whether deployment changes require a rollout.

  • #15004 e20df20 Thanks @MattieTK! - Delegate agent Pages project creation with a production branch to Workers

    When run by an AI agent, wrangler pages project create --production-branch <name> is now eligible for delegation to a Workers static-assets deploy. The production branch names the target that a Workers deploy would publish to, so it does not need to disqualify a brand-new project from delegation.

    wrangler pages deploy --branch <name> remains on Pages because an interactive new-project flow separately prompts for its production branch. The deployment branch may therefore represent a preview and cannot safely be converted into a production Workers deployment.

  • #15004 e20df20 Thanks @MattieTK! - Widen agent Pages-to-Workers delegation to new projects on accounts that already use Pages

    When run by an AI agent, wrangler pages deploy and wrangler pages project create now delegate a brand-new static Pages project to a Workers static-assets deploy even when the account already has other Pages projects. The gate is now per-project rather than per-account: a command targeting a project that already exists stays on Pages, but a new project is delegated regardless of the account's other Pages projects.

    A project name restored from the Pages configuration cache is only used when the cache belongs to the currently authenticated account. An account-matching cached name remains on Pages even when the project is missing remotely, preserving the user's recorded Pages intent. After switching accounts, an otherwise unnamed deploy stays on Pages rather than treating a stale cached project name as a new project on the selected account.

Patch Changes

  • #15560 edb3631 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @cloudflare/workers-types ^5.20260907.1 ^5.20260908.1
    workerd 1.20260907.1 1.20260908.1
  • #15557 63c7ff1 Thanks @tomekancu! - Fix wrangler d1 execute --local being extremely slow with large SQL files or commands

    The local SQL splitter consumed quoted strings and comments character-by-character, re-checking the full accumulated string each time. This made splitting a large quoted value or comment quadratic, so seed files could take tens of seconds to run. The splitter now only inspects a bounded trailing window on each step, making splitting effectively linear. The remote path is unaffected as it imports the file server-side.

  • #15542 a4e41df Thanks @NAVEENKUMARKR777! - Fix wrangler dev running the custom build command twice on startup and on every config change

    Wrangler already runs the custom build.command once before starting wrangler dev, to resolve the Worker's entry point. When dev.watch wasn't explicitly disabled, BundlerController then unconditionally ran the same build command again the moment it started watching for changes, and repeated this on every subsequent config reload too.

    For fast build commands this just meant duplicate log output (e.g. a vite build visibly running twice at startup). For slower or stateful build commands, running two builds concurrently against the same output files could corrupt the result or fail outright (for example, non-deterministic wasm-opt failures have been reported for Rust builds).

    The initial watcher setup now only bundles the output the build command already produced, instead of re-running the command. Real file changes detected by the watcher still re-run the build command as before.

  • Updated dependencies [edb3631, bcebf08]:

@cloudflare/autoconfig@0.4.3

Patch Changes

  • Updated dependencies [9c60d14, a849e0d]:
    • @cloudflare/config@0.11.0
    • @cloudflare/workers-utils@0.37.0
    • @cloudflare/cli-shared-helpers@0.1.28

@cloudflare/build-output-utils@0.4.1

Patch Changes

  • Updated dependencies [9c60d14]:
    • @cloudflare/config@0.11.0

@cloudflare/cli-shared-helpers@0.1.28

Patch Changes

  • Updated dependencies [a849e0d]:
    • @cloudflare/workers-utils@0.37.0

@cloudflare/deploy-helpers@0.10.3

Patch Changes

@cloudflare/pages-shared@0.13.178

Patch Changes

@cloudflare/vite-plugin@1.54.6

Patch Changes

@cloudflare/vitest-plugin@1.1.6

Patch Changes

@cloudflare/workers-auth@0.6.10

Patch Changes

  • Updated dependencies [a849e0d]:
    • @cloudflare/workers-utils@0.37.0

@cloudflare/remote-bindings@0.0.21

Patch Changes

@cloudflare/runtime-types@0.0.23

Patch Changes

@devin-ai-integration devin-ai-integration Bot 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.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@pkg-pr-new

pkg-pr-new Bot commented Sep 7, 2026 •

Copy link
Copy Markdown
@cloudflare/autoconfig

npm i https://pkg.pr.new/@cloudflare/autoconfig@15555

@cloudflare/build-output-utils

npm i https://pkg.pr.new/@cloudflare/build-output-utils@15555

@cloudflare/codemods

npm i https://pkg.pr.new/@cloudflare/codemods@15555

@cloudflare/config

npm i https://pkg.pr.new/@cloudflare/config@15555

create-cloudflare

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

@cloudflare/deploy-helpers

npm i https://pkg.pr.new/@cloudflare/deploy-helpers@15555

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-functions

npm i https://pkg.pr.new/@cloudflare/pages-functions@15555

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-plugin

npm i https://pkg.pr.new/@cloudflare/vitest-plugin@15555

@cloudflare/workers-auth

npm i https://pkg.pr.new/@cloudflare/workers-auth@15555

@cloudflare/workers-editor-shared

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

@cloudflare/workers-utils

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

wrangler

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

commit: 17b80e0

@workers-devprod
workers-devprod force-pushed the changeset-release/main branch 6 times, most recently from d9bcedd to 53173fb Compare September 8, 2026 15:35
@petebacondarwin
petebacondarwin merged commit 5705262 into main Sep 8, 2026
85 of 90 checks passed
@petebacondarwin
petebacondarwin deleted the changeset-release/main branch September 8, 2026 16:59
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.

2 participants