Skip to content

Update npm packages - #144

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-packages
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-packages

Conversation

@renovate

@renovate renovate Bot commented Nov 15, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@cloudflare/vitest-plugin (source) 1.6.0 → 1.8.1 age confidence
hono (source) 4.13.16 → 4.13.18 age confidence

Release Notes

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

v1.8.1

Compare Source

Patch Changes
  • #​16833 5f539b5 Thanks @​jamesopstad! - Name cf commands and settings in remote bindings errors

    When remote bindings could not authenticate, the error told you to run wrangler whoami, wrangler logout and wrangler login. It now names cf auth whoami, cf auth logout and cf auth login. When a Flagship binding without an id needed to run remotely, the error named Wrangler's app_id setting and suggested wrangler flagship apps create. It now names id and suggests cf flagship apps create.

    For the Vitest plugin, this applies to projects that load cloudflare.config.ts. Projects that use a Wrangler configuration file still see the Wrangler commands.

  • #​16834 8e57331 Thanks @​edmundhung! - Fix test files never finishing when a socket read rejects after a Worker handler has answered

    Previously, if a handler finished while a socket was still being read, for example a database client's connection, the read's rejection could leave vitest run waiting forever after the tests passed. Vitest now reports the unhandled error and the run ends.

  • Updated dependencies [8b2a363, 5f539b5, dc47e6d, 575d136, 3626ee8]:

v1.8.0

Compare Source

Minor Changes
  • #​16682 5966749 Thanks @​ghostwriternr! - Run the Containers that cloudflare.config.ts attaches to Durable Objects

    Previously, projects that load cloudflare.config.ts through the config option ran those Durable Objects without their Containers. The plugin now prepares the Containers' images and runs them, as it does for Wrangler configuration files. Dockerfile and build context paths are relative to the directory that contains cloudflare.config.ts.

    cloudflare.config.ts has no setting that disables local Containers, so, as with the Vite plugin, projects with Container-backed Durable Objects need Docker to run their tests.

Patch Changes
  • #​16824 877b249 Thanks @​jamesopstad! - Move streaming tail consumers to experimental.streamingTailConsumers in cloudflare.config.ts

    Streaming Tail Workers are now declared in a separate, experimental list instead of with streaming: true on a tailConsumers entry. tailConsumers now only lists Tail Workers with a tail() handler. This is a breaking change to the experimental config API: move each entry that set streaming: true to experimental.streamingTailConsumers, without the streaming field.

    export default defineConfig({
      worker: {
        tailConsumers: [{ worker: "tail-worker" }],
        experimental: {
          streamingTailConsumers: [{ worker: "streaming-tail-worker" }],
        },
      },
    });

    Fields under experimental may change or be removed without a major version bump. The wrangler-to-cf codemod now converts streaming_tail_consumers to experimental.streamingTailConsumers.

  • #​16734 c47cca7 Thanks @​matingathani! - Fix CommonJS dependencies being loaded as ES modules under Vitest 5 inline projects

    A dependency with its own "type": "commonjs" package.json was treated as an ES module when an earlier .js file elsewhere in the project had been classified by the project's "type": "module" package.json. The dependency then failed at import with errors such as Cannot set properties of undefined or exports is not defined. The nearest package.json now always decides how a .js file is loaded.

  • Updated dependencies [877b249, 69e650c]:

v1.7.0

Compare Source

Minor Changes
  • #​15695 d437be3 Thanks @​ghostwriternr! - Run the Containers that the Wrangler configuration attaches to Durable Objects

    Previously, the plugin disabled Containers, so those Durable Objects ran without ctx.container. The plugin now builds or pulls the Containers' images before each project's tests run and gives the Durable Objects a real ctx.container, so these projects now need Docker. To keep running their tests without Docker, set dev.enable_containers to false in the Wrangler configuration, which disables the Containers. Cloudflare-managed registry images are not supported yet.

Patch Changes

v1.6.1

Compare Source

Patch Changes
  • #​16793 fea323a Thanks @​vicb! - Bump capnp-es to 0.0.17

    This release fixes 3 issues. See the release notes for details.

  • #​16683 6f29f97 Thanks @​jamesopstad! - Stop persisting account selections made by cf and the Cloudflare Vite and Vitest plugins

    Profiles continue to select credentials rather than accounts. If the active credentials can access one account, it is selected automatically. If they can access multiple accounts, cf and the Vite and Vitest plugins reuse the selection while running but ask again the next time they start. Configure accountId in cloudflare.config.ts or set the CLOUDFLARE_ACCOUNT_ID environment variable to avoid repeated prompts.

    Wrangler's existing persistent account selection remains unchanged.

  • #​16648 56459a5 Thanks @​dario-piotrowicz! - Update bundled third-party dependencies with known security fixes

    Local development and Workers Vitest tests now include security fixes for their bundled dependencies. Local browser rendering also includes security fixes for browser downloads, archive extraction, and proxy support.

    Miniflare and Wrangler now require Node.js 22.12.0 or later, matching the supported runtime range of the new browser installer.

  • #​16746 abf924e Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-06

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #​16792 de10016 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-09

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #​15693 307a69a Thanks @​ghostwriternr! - Dispose Miniflare when a Vitest runtime fails to start

    Previously, a Miniflare instance whose startup failed was never disposed, so anything it had already started kept running. If disposal also fails, the original startup error is still reported.

  • #​16699 cd24b27 Thanks @​matingathani! - Fix vi.mock() factories failing under Vitest 5.1

    Mock factories in vi.mock() now work when running tests with Vitest 5.1 and later. Previously, any test file that used a mock factory failed during import with asyncLocalStorage.disable() is not implemented.

  • Updated dependencies [fea323a, a589d23, 56459a5, fe69809, abf924e, de10016, abf924e, de10016, 2fb01e7, dee7a1d, dc4e093, cff83d0, 3ef2afd, 4112820, 66bc0d6, cff83d0, 9b6582c, c64fdfb, 4112820]:

honojs/hono (hono)

v4.13.18

Compare Source

Security fixes

This release includes fixes for the following security issues:

validator() skips validation for requests whose Content-Type parameters are formatted differently

Affects: validator('json') and validator('form') in hono/validator. A Content-Type with whitespace before ;, a trailing ;, or an unusual parameter name was not recognized, so the validator saw an empty object while the handler could read all fields. This completes the fix for GHSA-4h7h-rv7c-7m2v. The validator now decides by the media type alone, as c.req.parseBody() does. GHSA-92p4-j3wq-jmqx

bodyLimit() keeps every transfer chunk of a request body in memory

Affects: bodyLimit() in hono/body-limit. A body sent in very small transfer chunks was retained as one object per chunk, so a request within the configured limit could exhaust memory. The body is now buffered in one array bounded by maxSize. GHSA-39q9-qp46-w8xg

mount() and app.mount() forward a wrong path when a custom getPath adds a prefix

Affects: mount() in hono/mount and app.mount() on 4.13.16 and 4.13.17. With a getPath that prepends a prefix such as the host name, one segment too many was removed from the forwarded path, so middleware scoped inside the mount prefix could be skipped. The prefix is removed from the routed path again. Paths that would change meaning when forwarded now get 400, and an optional regular expression parameter in a mount path throws. GHSA-h25j-2p75-qj33

serveStatic() serves a path that was decoded twice when allowPercentInPath is enabled

Affects: serveStatic() in hono/serve-static and the runtime adapters, only with allowPercentInPath: true. A malformed percent escape in the request path was decoded a second time, so a path that middleware registered on the encoded form did not see could still reach a static file. The file path must now be the same as the routed path, and otherwise the response is 404. GHSA-74fm-fwc7-3fwp


Users who rely on validator(), bodyLimit(), mount() with a custom getPath, or serveStatic() with allowPercentInPath are strongly encouraged to upgrade to this version.

Full Changelog: honojs/hono@v4.13.17...v4.13.18

v4.13.17

Compare Source

What's Changed

  • fix(cookie): match the __Secure- and __Host- prefixes case-insensitively in #​5608
  • fix(utils/url): do not match a query key across separators in #​5607
  • fix(etag,pretty-json): cancel the discarded response body in #​5606
  • fix(client): detect the JSON media type with whitespace before a parameter in #​5609
  • fix(timing): honor a precision of 0 in setMetric in #​5363
  • fix(utils/mime,ssg): match media types case-insensitively in #​5449
  • fix(timing): escape double quotes and backslashes in Server-Timing descriptions in #​5478
  • fix(etag): preserve commas within quoted entity tags in #​5353
  • fix(accepts): preserve exact media type quality over subtype wildcards in #​5427
  • fix(cookie): match the __Secure- and __Host- prefixes case-insensitively in CookieConstraint in #​5611
  • fix(jsx): add the CSP nonce to all scripts generated by ErrorBoundary in #​5430
  • fix(ssg): do not reuse created directories across toSSG runs in #​5381
  • fix(aws-lambda): sanitize non-ASCII header values in API Gateway v2 events in #​5483
  • fix(jsx): escape element and object attribute values in #​5512
  • fix(jsx): do not render ref objects as attributes in #​5615
  • fix(factory): keep independent return types for nine handlers in #​5618

Full Changelog: honojs/hono@v4.13.16...v4.13.17


Configuration

📅 Schedule: (in timezone Asia/Shanghai)

  • Branch creation
    • "before 10am on monday"
  • 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.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​cloudflare/​vitest-plugin@​1.6.0 ⏵ 1.8.19910081 +199 +1100
Updatedhono@​4.13.16 ⏵ 4.13.18100 +110097 +196 +1100

View full report

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.

0 participants