Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 17, 2025

This PR contains the following updates:

Package Change Age Confidence
@cloudflare/vitest-pool-workers (source) 0.10.5 -> 0.10.7 age confidence
@cloudflare/workers-types 4.20251109.0 -> 4.20251117.0 age confidence
@tsconfig/node-ts (source) 23.6.1 -> 23.6.2 age confidence
@tsconfig/node24 (source) 24.0.1 -> 24.0.2 age confidence
@tsconfig/strictest (source) 2.0.7 -> 2.0.8 age confidence
@types/node (source) 24.10.0 -> 24.10.1 age confidence
hono (source) 4.10.4 -> 4.10.6 age confidence
miniflare (source) 4.20251105.0 -> 4.20251109.1 age confidence
pnpm (source) 10.21.0 -> 10.22.0 age confidence
tsdown 0.16.1 -> 0.16.4 age confidence
wrangler (source) 4.46.0 -> 4.47.0 age confidence
xior 0.7.8 -> 0.8.0 age confidence

Release Notes

cloudflare/workers-sdk (@​cloudflare/vitest-pool-workers)

v0.10.7

Compare Source

Patch Changes

v0.10.6

Compare Source

Patch Changes
cloudflare/workerd (@​cloudflare/workers-types)

v4.20251117.0

Compare Source

v4.20251115.0

Compare Source

v4.20251113.0

Compare Source

v4.20251111.0

Compare Source

tsconfig/bases (@​tsconfig/node-ts)

v23.6.2

Compare Source

honojs/hono (hono)

v4.10.6

Compare Source

v4.10.5

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/hono@v4.10.4...v4.10.5

cloudflare/workers-sdk (miniflare)

v4.20251109.1

Compare Source

Patch Changes
  • #​11202 305ffb3 Thanks @​petebacondarwin! - Make Miniflare inspector proxy more resilient to selecting a free port

    We have seen some test flakes when there are a lot of Miniflare instances running in parallel.
    This appears to be that there is a small chance that a port becomes unavailable between checking if it is free and using it.

  • #​11231 46ccf0e Thanks @​connyay! - Fix WebSocket proxy timeout by disabling Node.js HTTP timeouts

    The dev registry proxy server was experiencing connection timeouts around
    60-90 seconds for long-lived WebSocket connections. This was caused by Node.js's
    headersTimeout (defaults to min(60s, requestTimeout)) which is checked periodically
    by connectionsCheckingInterval (defaults to 30s).

    When proxying WebSocket connections, the HTTP server's headers timeout was
    still active on the underlying socket, causing ERR_HTTP_REQUEST_TIMEOUT errors
    to be thrown and both client and server sockets to be destroyed.

    Setting both headersTimeout: 0 and requestTimeout: 0 in createServer options
    disables timeout enforcement, allowing WebSocket connections to remain open
    indefinitely as needed.

v4.20251109.0

Compare Source

Patch Changes
  • #​11200 dd7d584 Thanks @​dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251105.0 1.20251106.1
  • #​11232 4259256 Thanks @​dependabot! - chore: update dependencies of "miniflare" package

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20251106.1 1.20251109.0
pnpm/pnpm (pnpm)

v10.22.0

Compare Source

rolldown/tsdown (tsdown)

v0.16.4

Compare Source

   🚀 Features
    View changes on GitHub

v0.16.3

Compare Source

   🏎 Performance
    View changes on GitHub

v0.16.2

Compare Source

   🚀 Features
  • Upgrade rolldown to v1.0.0-beta.49  -  by @​sxzz (48181)
  • entry: Auto enable glob, support infer entry extension  -  by @​sxzz and jinghaihan (2c525)
    View changes on GitHub
cloudflare/workers-sdk (wrangler)

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
suhaotian/xior (xior)

v0.8.0

Compare Source

  • Feat: support xior(requestObj) syntax, Fix #​45
  • Feat: add isCancel util, re-export merge as mergeConfig util
  • Feat(Breaking change in Node/bun when use responseType: 'stream'): add xior/stream plugin, built it into package.json's node exports entry, now {responseType: 'stream'} is same behaviour with axios in nodejs; Fix #​46
  • Feat: re-export Xior* as Axios*, now you can just import {AxiosResponse, AxiosRequestConfig} from 'xior'
  • ci: skip ci tests when only markdown files are edited by @​kitsiosk in #​44
  • Chore: minor code and doc improvement
Breaking change:
  • if you use {responseType: 'stream'} in Node.js, follow the issue #​46 . Others platform like browser keep the original behaviour.

In Bun or node:

import axios from 'xior';

axios
  .request({
    method: 'get',
    url: 'https://bit.ly/2mTM3nY',
    responseType: 'stream',
  })
  .then(function (response) {
    response.data.pipe(fs.createWriteStream('ada_lovelace.jpg'));
  });

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 enabled auto-merge (squash) November 17, 2025 02:10
@renovate renovate bot merged commit a732740 into main Nov 17, 2025
5 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch November 17, 2025 02:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants