Skip to content

Version Packages#12427

Merged
ascorbic merged 1 commit intomainfrom
changeset-release/main
Feb 10, 2026
Merged

Version Packages#12427
ascorbic merged 1 commit intomainfrom
changeset-release/main

Conversation

@workers-devprod
Copy link
Copy Markdown
Contributor

@workers-devprod workers-devprod commented Feb 5, 2026

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

create-cloudflare@2.64.0

Minor Changes

  • #12286 5ddd276 Thanks @elithrar! - Add AGENTS.md to Workers templates for AI coding agent guidance

    New Workers projects created via create-cloudflare now include an AGENTS.md file that provides AI coding agents with retrieval-led guidance for Cloudflare APIs. This helps agents avoid using outdated knowledge from their training data and instead consult current documentation.

    The file includes:

    • Links to Cloudflare documentation and MCP servers
    • Essential wrangler commands (dev, deploy, types)
    • Pointers to product-specific documentation for limits and APIs
  • #12454 c99c437 Thanks @petebacondarwin! - Respect CLOUDFLARE_ACCOUNT_ID environment variable for account selection

    When the CLOUDFLARE_ACCOUNT_ID environment variable is set, C3 will now use it directly
    instead of prompting for account selection. This matches wrangler's behavior and enables
    seamless CI/CD workflows where the account is pre-configured via environment variables.

    Previously, C3 would always call wrangler whoami and prompt for account selection when
    multiple accounts were available, ignoring the environment variable.

Patch Changes

  • #12365 9eca052 Thanks @dependabot! - Update dependencies of "create-cloudflare"

    The following dependency versions have been updated:

    Dependency From To
    @angular/create 21.1.1 21.1.2
  • #12366 96d1605 Thanks @dependabot! - Update dependencies of "create-cloudflare"

    The following dependency versions have been updated:

    Dependency From To
    create-vue 3.20.0 3.21.0
  • #12367 9244501 Thanks @dependabot! - Update dependencies of "create-cloudflare"

    The following dependency versions have been updated:

    Dependency From To
    gatsby 5.15.0 5.16.0
  • #12481 0ac76d5 Thanks @dependabot! - Update dependencies of "create-cloudflare"

    The following dependency versions have been updated:

    Dependency From To
    create-vike 0.0.572 0.0.575

miniflare@4.20260210.0

Minor Changes

  • #12469 2d90127 Thanks @petebacondarwin! - Add environment variables to control cf.json fetching behavior

    You can now use environment variables to control how Miniflare handles the Request.cf object caching:

    • CLOUDFLARE_CF_FETCH_ENABLED - Set to "false" to disable fetching entirely and use fallback data. No node_modules/.mf/cf.json file will be created. Defaults to "true".
    • CLOUDFLARE_CF_FETCH_PATH - Set to a custom path to use a different location for caching the cf.json file instead of the default node_modules/.mf/cf.json.

    This is particularly useful for non-JavaScript projects (like Rust or Go Workers) that don't want a node_modules directory created automatically.

    Example:

    # Disable cf fetching for all projects
    export CLOUDFLARE_CF_FETCH_ENABLED=false
    npx wrangler dev
    
    # Or use a custom cache location
    export CLOUDFLARE_CF_FETCH_PATH=/tmp/.cf-cache.json
    npx wrangler dev
  • #12391 ce9dc01 Thanks @emily-shen! - Serve the local explorer UI from Miniflare

    This bundles the local explorer UI into Miniflare, and if enabled, Miniflare serves the UI at /cdn-cgi/explorer.

    This is an experimental, WIP feature.

Patch Changes

  • #12440 555b32a Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260205.0 1.20260206.0
  • #12485 d636d6a Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260206.0 1.20260207.0
  • #12502 bf8df0c Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260207.0 1.20260210.0

@cloudflare/vite-plugin@1.24.0

Minor Changes

  • #12446 1231a2e Thanks @jamesopstad! - Infer upload_source_maps setting in the output Worker config from the build.sourcemap setting in the Vite config.

    If build.sourcemap is enabled for a Worker environment, as in the following example, "upload_source_maps": true will now automatically be added to the output wrangler.json file.
    This removes the need to additionally specify the upload_source_maps property in the input Worker config.

    export default defineConfig({
    	environments: {
    		my_worker: {
    			build: {
    				sourcemap: true,
    			},
    		},
    	},
    	plugins: [cloudflare()],
    });

    Note that if upload_source_maps is set in the input Worker config, this value will take precedence.
    This makes it possible to generate source maps without uploading them.

Patch Changes

wrangler@4.64.0

Minor Changes

  • #12433 2acb277 Thanks @martinezjandrew! - Updated registries delete subcommand to handle new API response that now returns a secrets store secret reference after deletion. Wrangler will now prompt the user if they want to delete the associated secret. If so, added new logic to retrieve a secret by its name. The subcommand will then delete the secret.

  • #12307 e02b5f5 Thanks @dario-piotrowicz! - Improve autoconfig telemetry with granular event tracking

    Adds detailed telemetry events to track the autoconfig workflow, including process start/end, detection, and configuration phases. Each event includes a unique session ID (appId), CI detection, framework information, and success/error status to help diagnose issues and understand usage patterns.

  • #12474 8ba1d11 Thanks @petebacondarwin! - Add wrangler pages deployment delete command to delete Pages deployments via CLI

    You can now delete a Pages deployment directly from the command line:

    wrangler pages deployment delete <deployment-id> --project-name <name>

    Use the --force (or -f) flag to skip the confirmation prompt, which is useful for CI/CD automation.

  • #12307 e02b5f5 Thanks @dario-piotrowicz! - Include all common telemetry properties in ad-hoc telemetry events

    Previously, only command-based telemetry events (e.g., "wrangler command started/completed") included the full set of common properties. Ad-hoc events sent via sendAdhocEvent were missing important context like OS information, CI detection, and session tracking.

    Now, all telemetry events include the complete set of common properties:

    • amplitude_session_id and amplitude_event_id for session tracking
    • wranglerVersion (and major/minor/patch variants)
    • osPlatform, osVersion, nodeVersion
    • packageManager
    • configFileType
    • isCI, isPagesCI, isWorkersCI
    • isInteractive
    • isFirstUsage
    • hasAssets
    • agent
  • #12479 fd902aa Thanks @dario-piotrowicz! - Add framework selection prompt during autoconfig

    When running autoconfig in interactive mode, users are now prompted to confirm or change the detected framework. This allows correcting misdetected frameworks or selecting a framework when none was detected, defaulting to "Static" in that case.

  • #12465 961705c Thanks @petebacondarwin! - Add --json flag to wrangler pages project list command

    You can now use the --json flag to output the project list as clean JSON instead of a formatted table. This enables easier programmatic processing and scripting workflows.

    > wrangler pages project list --json
    
    [
      {
        "Project Name": "my-pages-project",
        "Project Domains": "my-pages-project-57h.pages.dev",
        "Git Provider": "No",
        "Last Modified": "23 hours ago"
      },
      ...
    ]
  • #12470 21ac7ab Thanks @petebacondarwin! - Add WRANGLER_COMMAND environment variable to custom build commands

    When using a custom build command in wrangler.toml, you can now detect whether wrangler dev or wrangler deploy triggered the build by reading the WRANGLER_COMMAND environment variable.

    This variable will be set to "dev", "deploy", "versions upload", or "types" depending on which command invoked the build. This allows you to customize your build process based on the deployment context.

    Example usage in a build script:

    if [ "$WRANGLER_COMMAND" = "dev" ]; then
      echo "Building for development..."
    else
      echo "Building for production..."
    fi

Patch Changes

  • #12468 5d56487 Thanks @petebacondarwin! - Add debug logs for git branch detection in wrangler pages deploy command

    When running wrangler pages deploy, the command automatically detects git information (branch, commit hash, commit message, dirty state) from the local repository. Previously, when this detection failed, there was no way to troubleshoot the issue.

    Now, running with WRANGLER_LOG=debug will output detailed information about:

    • Whether a git repository is detected
    • Each git command being executed and its result
    • The detected values (branch, commit hash, commit message, dirty status)
    • Any errors that occur during detection

    Example usage:

    WRANGLER_LOG=debug wrangler pages deploy ./dist --project-name=my-project
  • #12447 c8dda16 Thanks @dario-piotrowicz! - fix: Throw a descriptive error when autoconfig cannot detect an output directory

    When running wrangler setup or wrangler deploy --x-autoconfig on a project where the output directory cannot be detected, you will now see a clear error message explaining what's missing (e.g., "Could not detect a directory containing the static (html, css and js) files for the project") instead of a generic configuration error. This makes it easier to understand and resolve the issue.

  • #12440 555b32a Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260205.0 1.20260206.0
  • #12485 d636d6a Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260206.0 1.20260207.0
  • #12502 bf8df0c Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260207.0 1.20260210.0
  • #12280 988dea9 Thanks @penalosa! - Fix wrangler init failing with Yarn Classic

    When using Yarn Classic (v1.x), running wrangler init or wrangler init --from-dash would fail because Yarn Classic doesn't properly handle version specifiers with special characters like ^ in yarn create commands. Yarn would install the package correctly but then fail to find the binary because it would look for a path like .yarn/bin/create-cloudflare@^2.5.0 instead of .yarn/bin/create-cloudflare.

    This fix removes the version specifier from the default C3 command entirely. Since C3 has had auto-update behavior for over two years, specifying a version is no longer necessary and removing it resolves the Yarn Classic compatibility issue.

  • #12486 1f1c3ce Thanks @vicb! - Bump esbuild to 0.27.3

    This update includes several bug fixes from esbuild versions 0.27.1 through 0.27.3. See the esbuild changelog for details.

  • #12472 62635a0 Thanks @petebacondarwin! - Improve D1 database limit error message to match Cloudflare dashboard

    When attempting to create a D1 database after reaching your account's limit, the CLI now shows a more helpful error message with actionable guidance instead of the raw API error.

    The new message includes:

    • A clear explanation that the account limit has been reached
    • A link to D1 documentation
    • Commands to list and delete databases
  • #12411 355c6da Thanks @jbwcloudflare! - Fix wrangler pages deploy to respect increased file count limits

  • #12449 bfd17cd Thanks @penalosa! - fix: Display unsafe metadata separately from bindings

    Unsafe metadata are not bindings and should not be displayed in the bindings table. They are now printed as a separate JSON block.

    Before:

    Your Worker has access to the following bindings:
    Binding                               Resource
    env.extra_data ("interesting value")  Unsafe Metadata
    env.more_data ("dubious value")       Unsafe Metadata
    

    After:

    The following unsafe metadata will be attached to your Worker:
    {
      "extra_data": "interesting value",
      "more_data": "dubious value"
    }
    
  • #12463 3388c84 Thanks @petebacondarwin! - Add User-Agent header to remote dev inspector WebSocket connections

    When running wrangler dev --remote, the inspector WebSocket connection now includes a User-Agent header (wrangler/<version>). This resolves issues where WAF rules blocking empty User-Agent headers prevented remote dev mode from working with custom domains.

  • #12421 937425c Thanks @ryanking13! - Fix Python Workers deployment failing on Windows due to path separator handling

    Previously, deploying Python Workers on Windows would fail because the backslash path separator (\) was not properly handled, causing the entire full path to be treated as a single filename. The deployment process now correctly normalizes paths to use forward slashes on all platforms.

  • Updated dependencies [2d90127, 555b32a, d636d6a, bf8df0c, 312b5eb, ce9dc01]:

    • miniflare@4.20260210.0
    • @cloudflare/unenv-preset@2.12.1

@cloudflare/pages-shared@0.13.106

Patch Changes

@cloudflare/unenv-preset@2.12.1

Patch Changes

  • #12377 312b5eb Thanks @vicb! - Use the native node:process v2 when it is available

    Note that we only enable this if all of the following conditions are met:

    • compatibility_date >= 2025-09-15 or process v2 enabled by flag (enable_nodejs_process_v2)
    • fetch_iterable_type_support and fetch_iterable_type_support_override_adjustment are active (explicitly specified or implied by date or other flags).

    Note that EventEmitters (on, off, addListener, removeListener, ...) used to be available on the imported process module while they should not have been. They are now only available on the global process:

    import p from "node:process";
    
    // Working before this PR, not working after this PR
    p.on("exit", exitHandler);
    
    // Use the global process instead (works before and after the PR)
    process.on("exit", exitHandler);

@cloudflare/vitest-pool-workers@0.12.11

Patch Changes

@cloudflare/containers-shared@0.9.0

Minor Changes

  • #12433 2acb277 Thanks @martinezjandrew! - Updated registries delete subcommand to handle new API response that now returns a secrets store secret reference after deletion. Wrangler will now prompt the user if they want to delete the associated secret. If so, added new logic to retrieve a secret by its name. The subcommand will then delete the secret.

@cloudflare/local-explorer-ui@0.2.0

Minor Changes

  • #12459 e3e9ca9 Thanks @NuroDev! - Add dark mode support to the local explorer UI

    This includes adding an initial implementation that uses your preferred system theme to select what theme to render the local explorer UI in.

    Additionally, this includes a number of minor style tweaks & fixes.

    This is an experimental WIP feature.

  • #12391 ce9dc01 Thanks @emily-shen! - Serve the local explorer UI from Miniflare

    This bundles the local explorer UI into Miniflare, and if enabled, Miniflare serves the UI at /cdn-cgi/explorer.

    This is an experimental, WIP feature.

Patch Changes

  • #12414 de473c2 Thanks @emily-shen! - Change the favicon to a Cloudflare logo outline

    This is for an experimental WIP project.

@cloudflare/workers-shared@0.19.0

Minor Changes

  • #12467 7036310 Thanks @petebacondarwin! - Add support for inline comments in _redirects files

    You can now add inline comments to redirect rules using the # character:

    /old-page /new-page 301 # Moved during site redesign
    /blog/* /articles/:splat # Blog URL migration
    

    This improves the maintainability of _redirects files by allowing documentation of complex redirect rules directly alongside the rules themselves. Full-line comments (lines starting with #) continue to work as before. URL fragments (e.g., /page#section) are preserved correctly.

@cloudflare/devprod-status-bot@1.4.1

Patch Changes

  • #12435 c2163df Thanks @petebacondarwin! - Simplify Version Packages PR CI failure alerts

    The bot now sends an alert for any failing CI job on the Version Packages PR, instead of first fetching the required status checks from GitHub's branch protection API and filtering. This removes unnecessary complexity and ensures all CI failures are reported.

@workers-devprod workers-devprod requested review from a team as code owners February 5, 2026 13:18
@claude
Copy link
Copy Markdown
Contributor

claude Bot commented Feb 5, 2026

Claude finished @workers-devprod's task —— View job


Changeset Review

  • Analyze PR context
  • Review changeset files
  • Provide feedback

Review Results

This is a Version Packages PR created by the Changesets release action. The changeset files you've asked me to review have already been consumed and processed:

  • All .changeset/*.md files have been deleted (marked as DELETED in the PR)
  • Their content has been transformed into CHANGELOG.md entries across the affected packages
  • Version numbers have been bumped in package.json files

What this means:

The changesets were already validated and processed by the Changesets GitHub action when it created this PR. The original changeset files no longer exist because they've been consumed during the release preparation process. The changes are now reflected in:

  • packages/*/CHANGELOG.md files (with formatted release notes)
  • packages/*/package.json files (with version bumps)

For Version Packages PRs, the review focus should typically be on:

  • Verifying the generated CHANGELOG entries are correctly formatted
  • Confirming version bumps follow semver correctly
  • Checking that package dependencies are updated appropriately

If you'd like me to review the generated CHANGELOG entries or verify the version bumps instead, please let me know!


Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

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.

Open in Devin Review

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented Feb 5, 2026

create-cloudflare

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

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-pool-workers

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

@cloudflare/workers-editor-shared

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

@cloudflare/workers-utils

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

wrangler

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

commit: ee885c3

@workers-devprod workers-devprod force-pushed the changeset-release/main branch 9 times, most recently from 5107d7f to 8752ff8 Compare February 5, 2026 18:22
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

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.

Open in Devin Review

@workers-devprod workers-devprod force-pushed the changeset-release/main branch 13 times, most recently from e5b3be6 to e73f19a Compare February 8, 2026 14:23
@workers-devprod workers-devprod force-pushed the changeset-release/main branch 21 times, most recently from dbcdade to 575291e Compare February 9, 2026 21:21
@ascorbic ascorbic merged commit 04eac7d into main Feb 10, 2026
38 checks passed
@ascorbic ascorbic deleted the changeset-release/main branch February 10, 2026 09:18
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.

3 participants