Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 13, 2025

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
wrangler (source) ^3.99.0 -> ^4.0.0 age confidence

Release Notes

cloudflare/workers-sdk (wrangler)

v4.53.0

Compare Source

Minor Changes
  • #​11500 af54c63 Thanks @​dario-piotrowicz! - Add new autoconfig_summary field to the deploy output entry

    This change augments wrangler deploy output being printed to WRANGLER_OUTPUT_FILE_DIRECTORY or WRANGLER_OUTPUT_FILE_PATH to also include a new autoconfig_summary field containing the possible summary details for the autoconfig process (the field is undefined if autoconfig didn't run).

    Note: the field is experimental and could change while autoconfig is not GA

  • #​11477 9988cc9 Thanks @​ascorbic! - Support Nuxt in autoconfig

  • #​11472 ce295bf Thanks @​dario-piotrowicz! - Support Qwik projects in autoconfig

  • #​10937 9514c9a Thanks @​ReppCodes! - Add support for "targeted" placement mode with region, host, and hostname fields

    This change adds a new mode to placement configuration. You can specify one of the following fields to target specific external resources for Worker placement:

    • region: Specify a region identifier (e.g., "aws:us-east-1") to target a region from another cloud service provider
    • host: Specify a host with (required) port (e.g., "example.com:8123") to target a TCP service
    • hostname: Specify a hostname (e.g., "example.com") to target an HTTP resource

    These fields are mutually exclusive - only one can be specified at a time.

    Example configuration:

    [placement]
    host = "example.com:8123"
  • #​11498 ac861f8 Thanks @​penalosa! - Add React Router support in autoconfig

  • #​11506 79d30d4 Thanks @​vicb! - Set the target JS version to ES2024

Patch Changes

v4.52.1

Compare Source

Patch Changes

v4.52.0

Compare Source

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

  • #​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.

  • #​11375 9a1de61 Thanks @​penalosa! - Support TanStack Start in autoconfig

  • #​11360 6b38532 Thanks @​emily-shen! - Containers: Allow users to directly authenticate external image registries in local dev

    Previously, we always queried the API for stored registry credentials and used those to pull images. This means that if you are using an external registry (ECR, dockerhub) then you have to configure registry credentials remotely before running local dev.

    Now you can directly authenticate with your external registry provider (using docker login etc.), and Wrangler or Vite will be able to pull the image specified in the containers.image field in your config file.

    The Cloudflare-managed registry (registry.cloudflare.com) currently still does not work with the Vite plugin.

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

  • #​11478 2aec2b4 Thanks @​dario-piotrowicz! - Support SolidStart in autoconfig

  • #​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 of eval() from the Wrangler bundle

  • #​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 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"
        }
      }
  • #​11484 1cfae2d Thanks @​edmundhung! - Explicitly close FileHandle in wrangler d1 execute to support Node 25

  • #​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 displaying 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]:

v4.51.0

Compare Source

Minor Changes
  • #​11345 d524e55 Thanks @​penalosa! - Enable experimental support for autoconfig-powered Astro projects

  • #​11228 43903a3 Thanks @​petebacondarwin! - Support CLOUDFLARE_ENV environment variable for selecting the active environment

    This change enables users to select the environment for commands such as CLOUDFLARE_ENV=prod wrangler versions upload. The --env command line argument takes precedence.

    The CLOUDFLARE_ENV environment variable is mostly used with the @cloudflare/vite-plugin to select the environment for building the Worker to be deployed. This build also generates a "redirected deploy config" that is flattened to only contain the active environment.
    To avoid accidentally deploying a version that is built for one environment to a different environment, there is an additional check to ensure that if the user specifies an environment in Wrangler it matches the original selected environment from the build.

Patch Changes

v4.50.0

Compare Source

Minor Changes
  • #​11219 524a6e5 Thanks @​Ltadrian! - Implement Hyperdrive binding TLS miniflare proxy. This will allow for wrangler dev hyperdrive bindings to connect to external
    databases that require TLS.

  • #​11233 c922a81 Thanks @​emily-shen! - Add containers.unsafe to allow internal users to use additional container features

Patch Changes

v4.49.1

Compare Source

Patch Changes

v4.49.0

Compare Source

Minor Changes
  • #​10703 c5c4ee5 Thanks @​danlapid! - Add support for streaming tail consumers in local dev. This is an experimental new feature that allows you to register a tailStream() handler (compared to the existing tail() handler), which will receive streamed tail events from your Worker (compared to the tail() handler, which only receives batched events after your Worker has finished processing).

  • #​11251 7035804 Thanks @​penalosa! - When the WRANGLER_HIDE_BANNER environment variable is provided, Wrangler will no longer display a version banner. This applies to all commands.

    For instance, previously running wrangler docs would give the following output:

    > wrangler docs
     ⛅️ wrangler 4.47.0
    ───────────────────
    Opening a link in your default browser: https://developers.cloudflare.com/workers/wrangler/commands/
    

    With WRANGLER_HIDE_BANNER, this is now:

    > WRANGLER_HIDE_BANNER=true wrangler docs
    Opening a link in your default browser: https://developers.cloudflare.com/workers/wrangler/commands/
    
  • #​11285 d014fa7 Thanks @​vicb! - Implement the wrangler r2 bulk put bucket-name --filename list.json command.

    The command uploads multiple objects to an R2 bucket.

    The list of object is provided as a JSON encoded file via --filename. It is a list of key and file (respectively the name and the content for the object).

    [
      { "key": "/path/to/obj", "file": "/path/to/file_1"},
      { "key": "/path/to/other/obj", "file": "/path/to/file_2"},
      // ...
    ]
    

    Uploads are executed concurrently and the level of concurrency can be set via --concurrency.

    The command supports the same options as wrangler r2 object put, minus --file, and --pipe and plus --concurrency

  • #​11268 15b8460 Thanks @​penalosa! - Support SvelteKit projects in autoconfig

  • #​11258 2011b6a Thanks @​dario-piotrowicz! - Add --dry-run flag to wrangler setup and also a dryRun option to runAutoConfig

Patch Changes

v4.48.0

Compare Source

Minor Changes
  • #​11212 3908162 Thanks @​dario-piotrowicz! - Add autoconfig changes summary for wrangler deploy --x-autoconfig with the option for users to cancel the operation

  • #​11229 14d79f2 Thanks @​dario-piotrowicz! - Enables experimental-deploy-remote-diff-check flag by default (the flag is still present for now so that users can turn it off if needed) and improves the remote config diffing logic (to include less noise in the diff presented to the user)

  • #​11245 dfc6513 Thanks @​vicb! - Change how Wrangler selects default ports for dev sessions.

    If no port is specified, Wrangler now probes the default port and the 10 consecutive ports after it before falling back to a random port.
    This will help getting a stable port number across dev sessions.
    Both the http server and inspector ports are affected.

Patch Changes

v4.47.0

Compare Source

Minor Changes
  • #​11201 5286309 Thanks @​avenceslau! - Add wrangler workflows instances restart command

  • #​11214 5cf8a39 Thanks @​penalosa! - Add the experimental wrangler setup command to run autoconfig outside of the deploy flow.

  • #​11187 8abc789 Thanks @​dario-piotrowicz! - Add possibility for users to edit their project settings during autoconfig

    When running wrangler deploy --experimental-autoconfig, after the automatic project settings detection Wrangler will now present users the opportunity to customize the auto-detected project's settings

Patch Changes

v4.46.0

Compare Source

Minor Changes
Patch Changes
  • #​11160 05440a1 Thanks @​dario-piotrowicz! - Allows auto-update of the local Wrangler configuration file to match remote configuration when running wrangler deploy --env <TARGET_ENV>

    When running wrangler deploy, with --x-remote-diff-check and after cancelling the deployment due to destructive changes present in the local config file, Wrangler offers to update the Wrangler configuration file to match the remote configuration. This wasn't however enabled when a target environment was specified (via the --env|-e flag). Now this will also apply when an environment is targeted.

  • #​11162 c3ed531 Thanks @​dario-piotrowicz! - Update the description of the --local flag for the wrangler dev command to clarify that it disables remote bindings, also un-deprecate and un-hide it

  • #​11162 c3ed531 Thanks @​dario-piotrowicz! - Fix bindings with remote: true being logged as remote when run via wrangler dev --local

  • Updated dependencies [1ae020d]:

    • miniflare@​4.20251105.0

v4.45.4

Compare Source

Patch Changes
  • #​11133 8ffbd17 Thanks @​petebacondarwin! - Reduce the amount of arguments being passed in metrics capture.

    Now the argument values that are captured come from an allow list,
    and can be marked as ALLOW (capture the real value) or REDACT (capture as "").

  • #​11033 77ed7e2 Thanks @​dario-piotrowicz! - Offer to update the local Wrangler configuration file to match remote configuration when running wrangler deploy

    When running wrangler deploy, with --x-remote-diff-check, Wrangler will display the difference between local and remote configuration.
    If there would be a destructive change to the remote configuration, the user is given the option to cancel the deployment.
    In the case where the user does cancel deployment, Wrangler will now also offer to update the local Wrangler configuration file to match the remote configuration.

  • #​11139 bb00f9d Thanks @​devin-ai-integration! - Updated cron trigger documentation links and improved error message to include instructions for testing cron triggers locally

  • #​11135 ed666a1 Thanks @​penalosa! - Implement tail-based logging for wrangler dev remote mode, behind the --x-tail-tags flag. This will become the default in the future.

  • #​11149 22f25fd Thanks @​penalosa! - Add no-op autoconfig logic behind an experimental flag

  • Updated dependencies [90a2566, 14f60e8]:

v4.45.3

Patch Changes
  • #​11117 6822aaf Thanks @​emily-shen! - fix: show local/remote status before D1 command confirmations

    D1 commands (execute, export, migrations apply, migrations list, delete, time-travel) now display whether they're running against local or remote databases before showing confirmation prompts. This prevents confusion about which database will be affected by the operation.

  • #​11077 bce8142 Thanks @​petebacondarwin! - Ensure that process.env is case-insensitive on Windows

    The object that holds the environment variables in process.env does not care about the case of its keys
    in Windows. For example, process.env.SystemRoot and process.env.SYSTEMROOT will refer to the same value.

    Previously, when merging fields from .env files we were replacing this native object with a vanilla
    JavaScript object, that is case-insensitive, and so sometimes environment variables appeared to be missing
    when in reality they just had different casing.

v4.45.2

Patch Changes

v4.45.1

Compare Source

Patch Changes

v4.45.0

Compare Source

Minor Changes
  • #​11030 1a8088a Thanks @​penalosa! - Enable automatic resource provisioning by default in Wrangler. This is still an experimental feature, but we're turning on the flag by default to make it easier for people to test it and try it out. You can disable the feature using the --no-x-provision flag. It currently works for R2, D1, and KV bindings.

    To use this feature, add a binding to your config file without a resource ID:

    {
    	"kv_namespaces": [{ "binding": "MY_KV" }],
    	"d1_databases": [{ "binding": "MY_DB" }],
    	"r2_buckets": [{ "binding": "MY_R2" }],
    }

    wrangler dev will automatically create these resources for you locally, and when you next run wrangler deploy Wrangler will call the Cloudflare API to create the requested resources and link them to your Worker. They'll stay linked across deploys, and you don't need to add the resource IDs to the config file for future deploys to work. This is especially good for shared templates, which now no longer need to include account-specific resource ID when adding a binding.

Patch Changes
  • #​11037 4bd4c29 Thanks @​danielrs! - Better Wrangler subdomain defaults warning.

    Improves the warnings that we show users when either worker_dev or preview_urls are missing.

  • #​10927 31e1330 Thanks @​dom96! - Implements python_modules.excludes wrangler config field

    [python_modules]
    excludes = ["**/*.pyc", "**/__pycache__"]
  • #​10741 2f57345 Thanks @​penalosa! - Remove obsolete --x-remote-bindings flag

  • Updated dependencies [ca6c010]:

    • miniflare@​4.20251011.1

v4.44.0

Compare Source

Minor Changes
  • #​10939 d4b4c90 Thanks @​danielrs! - Config preview_urls defaults to workers_dev value.

    Originally, we were defaulting config.preview_urls to true, but we
    were accidentally enabling Preview URLs for users that only had
    config.workers_dev=false.

    Then, we set the default value of config.preview_urls to false, but we
    were accidentally disabling Preview URLs for users that only had
    config.workers_dev=true.

    Rather than defaulting config.preview_urls to true or false, we
    default to the resolved value of config.workers_dev. Should result in a
    clearer user experience.

  • #​11027 1a2bbf8 Thanks @​jamesopstad! - Statically replace the value of process.env.NODE_ENV with development for development builds and production for production builds if it is not set. Else, use the given value. This ensures that libraries, such as React, that branch code based on process.env.NODE_ENV can be properly tree shaken.

  • #​9705 0ee1a68 Thanks @​hiendv! - Add params type to Workflow type generation. E.g.

    interface Env {
    	MY_WORKFLOW: Workflow<
    		Parameters<import("./src/index").MyWorkflow["run"]>[0]["payload"]
    	>;
    }
  • #​10867 dd5f769 Thanks @​austin-mc! - Add media binding support

Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot temporarily deployed to cloudflare-pages March 13, 2025 16:36 Inactive
@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Mar 13, 2025

Deploying auth-wiki with  Cloudflare Pages  Cloudflare Pages

Latest commit: 7ae565f
Status: ✅  Deploy successful!
Preview URL: https://d5662a2c.auth-wiki.pages.dev
Branch Preview URL: https://renovate-wrangler-4-x.auth-wiki.pages.dev

View logs

@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 849cd87 to 328b580 Compare April 10, 2025 13:57
@renovate renovate bot temporarily deployed to cloudflare-pages April 10, 2025 13:57 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 328b580 to 0b8de61 Compare April 10, 2025 16:41
@renovate renovate bot temporarily deployed to cloudflare-pages April 10, 2025 16:41 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 0b8de61 to 4a53e8d Compare June 30, 2025 07:20
@renovate renovate bot temporarily deployed to cloudflare-pages June 30, 2025 07:20 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 4a53e8d to 8db9180 Compare July 22, 2025 18:26
@renovate renovate bot temporarily deployed to cloudflare-pages July 22, 2025 18:26 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 8db9180 to 38e2537 Compare July 24, 2025 17:50
@renovate renovate bot temporarily deployed to cloudflare-pages July 24, 2025 17:50 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 38e2537 to 7915a1a Compare July 29, 2025 11:48
@renovate renovate bot temporarily deployed to cloudflare-pages July 29, 2025 11:48 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 7915a1a to f755880 Compare July 31, 2025 16:57
@renovate renovate bot temporarily deployed to cloudflare-pages July 31, 2025 16:57 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from f755880 to 8ba1ff2 Compare August 5, 2025 10:12
@renovate renovate bot temporarily deployed to cloudflare-pages August 5, 2025 10:13 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 8ba1ff2 to ae902e1 Compare August 7, 2025 02:24
@renovate renovate bot temporarily deployed to cloudflare-pages August 7, 2025 02:24 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from ae902e1 to 8da841b Compare August 7, 2025 12:40
@renovate renovate bot temporarily deployed to cloudflare-pages August 7, 2025 12:41 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 8da841b to fe8927b Compare August 12, 2025 19:01
@renovate renovate bot temporarily deployed to cloudflare-pages August 12, 2025 19:01 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from fe8927b to 67f81aa Compare August 13, 2025 15:52
@renovate renovate bot temporarily deployed to cloudflare-pages August 13, 2025 15:52 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 67f81aa to 7b65a43 Compare August 14, 2025 16:50
@renovate renovate bot temporarily deployed to cloudflare-pages August 14, 2025 16:50 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 7b65a43 to cd1a021 Compare August 18, 2025 18:13
@renovate renovate bot had a problem deploying to cloudflare-pages August 18, 2025 18:13 Failure
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 6ed9db4 to 1693fee Compare October 29, 2025 19:42
@renovate renovate bot had a problem deploying to cloudflare-pages October 29, 2025 19:42 Failure
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 1693fee to 033a7cf Compare October 30, 2025 20:13
@renovate renovate bot temporarily deployed to cloudflare-pages October 30, 2025 20:13 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 033a7cf to f9f2299 Compare November 4, 2025 20:36
@renovate renovate bot temporarily deployed to cloudflare-pages November 4, 2025 20:36 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from f9f2299 to 3b50962 Compare November 6, 2025 18:01
@renovate renovate bot had a problem deploying to cloudflare-pages November 6, 2025 18:01 Failure
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from d1e1dae to 3d7c016 Compare November 13, 2025 12:11
@renovate renovate bot temporarily deployed to cloudflare-pages November 13, 2025 12:11 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 3d7c016 to 1dc23b6 Compare November 14, 2025 22:34
@renovate renovate bot had a problem deploying to cloudflare-pages November 14, 2025 22:34 Failure
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 1dc23b6 to 04b314e Compare November 18, 2025 22:28
@renovate renovate bot had a problem deploying to cloudflare-pages November 18, 2025 22:28 Failure
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 04b314e to ad1029a Compare November 20, 2025 13:36
@renovate renovate bot temporarily deployed to cloudflare-pages November 20, 2025 13:36 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from ad1029a to f3b22f6 Compare November 20, 2025 21:59
@renovate renovate bot had a problem deploying to cloudflare-pages November 20, 2025 21:59 Failure
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from f3b22f6 to 07828eb Compare November 26, 2025 17:29
@renovate renovate bot temporarily deployed to cloudflare-pages November 26, 2025 17:29 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 07828eb to b8416f0 Compare December 2, 2025 17:59
@renovate renovate bot had a problem deploying to cloudflare-pages December 2, 2025 17:59 Failure
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from b8416f0 to ddc46b5 Compare December 2, 2025 20:33
@renovate renovate bot temporarily deployed to cloudflare-pages December 2, 2025 20:33 Inactive
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from ddc46b5 to 7ae565f Compare December 3, 2025 18:51
@renovate renovate bot deployed to cloudflare-pages December 3, 2025 18:51 Active
@renovate renovate bot force-pushed the renovate/wrangler-4.x branch from 7ae565f to b7fa8d2 Compare December 5, 2025 04:05
@renovate renovate bot had a problem deploying to cloudflare-pages December 5, 2025 04:05 Failure
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant