Skip to content

fix(deps): update all non-major dependencies - #146

Open
khepri-bot[bot] wants to merge 1 commit into
mainfrom
renovate/all-non-major-dependencies
Open

fix(deps): update all non-major dependencies#146
khepri-bot[bot] wants to merge 1 commit into
mainfrom
renovate/all-non-major-dependencies

Conversation

@khepri-bot

@khepri-bot khepri-bot Bot commented Sep 7, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@cloudflare/vite-plugin (source) 1.52.1 → 1.56.0 age confidence devDependencies minor 1.62.5 (+15)
@cloudflare/vitest-pool-workers (source) 0.21.3 → 0.22.0 age confidence devDependencies minor
@fast-check/vitest (source) 0.4.1 → 0.5.0 age confidence devDependencies minor
@kobalte/core (source) 0.13.13 → 0.13.14 age confidence dependencies patch
@octokit/core 7.0.7 → 7.0.8 age confidence dependencies patch
@octokit/core 7.0.7 → 7.0.8 age confidence devDependencies patch
@playwright/test (source) 1.62.1 → 1.63.0 age confidence devDependencies minor
@sentry/cloudflare (source) 10.70.0 → 10.75.0 age confidence dependencies minor 11.4.0 (+8)
@sentry/solid (source) 10.70.0 → 10.75.0 age confidence dependencies minor 11.4.0 (+8)
@testing-library/user-event 14.6.4 → 14.6.7 age confidence devDependencies patch
@types/node (source) 26.2.0 → 26.6.2 age confidence devDependencies minor 26.6.4 (+1)
daisyui (source) 5.7.17 → 5.7.42 age confidence devDependencies patch 5.7.47 (+4)
happy-dom 20.11.2 → 20.14.5 age confidence devDependencies minor
node 24.19.0 → 24.21.0 age confidence uses-with minor
pnpm (source) 12.4.1 → 12.5.1 age confidence packageManager minor 12.9.1 (+6)
pnpm/action-setup v6.0.10 → v6.1.0 age confidence action minor
solid-js (source) 1.9.14 → 1.9.15 age confidence dependencies patch
tsx (source) 4.23.12 → 4.23.15 age confidence devDependencies patch
vite (source) 8.2.1 → 8.3.0 age confidence devDependencies minor 8.3.2 (+1)
wrangler (source) 4.123.0 → 4.135.0 age confidence devDependencies minor 4.147.0 (+15)
zod (source) 4.4.3 → 4.6.5 age confidence dependencies minor

Release Notes

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

v1.56.0

Compare Source

Minor Changes

  • #​15609 1f070c8 Thanks @​emily-shen! - Build Containers when emitting experimental Build Output

    Wrangler and the Cloudflare Vite plugin now build Dockerfile-backed Container images when experimental Build Output is enabled. Container configs are emitted under .cloudflare/output/v0/containers with local image references, while existing registry references pass through unchanged.

  • #​15329 c4c9b75 Thanks @​akshitsinha! - Evaluate Flagship flags locally during development

    Flagship bindings now use the local Miniflare store by default in Wrangler and the Vite plugin, keeping development offline and isolated from production flags. Set remote: true on a binding to continue using its remote app.

    Use wrangler flagship flags pull <APP_ID> to seed the store from a remote app. Flag management commands also accept --local to read and update the local store directly.

  • #​15701 643e5cc Thanks @​WillTaylorDev! - Pass Preview intent to defineWorker and upload its resolved configuration

    Preview builds now evaluate programmatic Worker configuration with ctx.isPreview set to true and record that intent in Build Output. The shared Preview uploader deploys the resolved bindings and settings while preserving configured Preview base values when it creates a Preview.

Patch Changes

v1.55.0

Compare Source

Minor Changes

  • #​15674 a939a6c Thanks @​ghostwriternr! - Support explicit named Container image selection in local development

    The Vite plugin builds or pulls named images from Wrangler configuration and exposes their local tags through ctx.container.images. Pass one of those references to ctx.container.start({ image }) to select the image.

    This extends the experimental Durable Object-managed Containers interface.

Patch Changes

v1.54.11

Compare Source

Patch Changes

v1.54.10

Compare Source

Patch Changes

  • #​14775 1be7b97 Thanks @​dario-piotrowicz! - Sync Local Explorer endpoint lists across agent hints

    The Local Explorer endpoint list is now consistent across the three places it appears: the AGENTS.md template in create-cloudflare, the runtime agent hint in wrangler dev, and the Vite plugin agent hint. All three now include the observability/clear endpoint, use the canonical /cdn-cgi/local/explorer path, and have cross-reference comments pointing to each other.

  • #​15399 982b806 Thanks @​tpmmorris! - Improve over-limit run_worker_first errors when duplicate rules are present

    The error now reports distinct and duplicate-entry counts and lists duplicated rules, making it clear when removing redundant entries can bring the configuration within the limit.

    Too many `run_worker_first` rules were provided; 105 rules provided (99 distinct, 6 duplicate entries) exceeds max of 100. Note: duplicate entries count towards the route limit. Ensure that no duplicate rules are present in your `run_worker_first` configuration.

The duplicated rules found are:
- "/rule/0"
- "/rule/1"
- "/rule/2"
- "/rule/3"
- "/rule/4"
...and 1 more duplicated rule.

  • Updated dependencies [1be7b97, b149147, 7db596c, 76c0ce6, a83d7ac, a0856da, e35c4a1, d3565a5, a83d7ac, cb0955f, fa79b26, 16d1310, ca71205, 1015cfb, 982b806, ffabe74, 7db596c, e03822a, a83d7ac, 641df47, c4a6279]:

v1.54.9

Compare Source

Patch Changes

  • #​15574 164e4fb Thanks @​RealBhupesh! - Ignore .wrangler persistence writes in Vite's file watcher

    Miniflare stores local D1, KV, R2, and observability state under .wrangler/state. Those writes were watched as source changes on Linux and Windows, which fired every plugin hotUpdate hook and could make page loads take seconds. The plugin now ignores **/.wrangler/** while preserving any server.watch.ignored patterns already set by the user.

  • Updated dependencies [8997652]:

v1.54.8

Compare Source

Patch Changes

v1.54.7

Compare Source

Patch Changes

v1.54.6

Compare Source

Patch Changes

v1.54.5

Compare Source

Patch Changes

  • #​15519 e004845 Thanks @​devaniketh! - Preserve HTTP/2 :authority header and non-default port in dev server requests

    When Vite runs over HTTPS with HTTP/2 enabled, browsers send authority via the :authority pseudo-header rather than Host. Previously, pseudo-headers were omitted when creating Fetch requests, causing non-default ports to be dropped from request.url and X-Forwarded-Host. Authority and scheme are now preserved from HTTP/2 pseudo-headers and request properties.

  • Updated dependencies [8bbcb9f, 2b42d6f, ea5634e, c0c6504, ffc7efd, 682cd44]:

v1.54.4

Compare Source

Patch Changes

v1.54.3

Compare Source

Patch Changes

v1.54.2

Compare Source

Patch Changes

v1.54.1

Compare Source

Patch Changes

v1.54.0

Compare Source

Minor Changes

  • #​15134 c66d2d5 Thanks @​gpanders! - Enable FUSE-capable local container development

    Miniflare now automatically passes the Docker privileges needed for FUSE to local Durable Object containers when using local rootless Docker on Linux with /dev/fuse available, or a local Docker engine on macOS or through WSL where Linux containers run in a VM. This applies to Wrangler, the Cloudflare Vite plugin, and direct Miniflare use.

  • #​15326 9fcb1c9 Thanks @​jamesopstad! - Record the selected mode in the Build Output Specification top-level config.json

    The mode a build was produced in is now written to .cloudflare/output/v0/config.json as a mode field, alongside the account and compliance settings.

Patch Changes

v1.53.1

Compare Source

Patch Changes

v1.53.0

Compare Source

Minor Changes

  • #​15026 6529f0c Thanks @​petebacondarwin! - Allow containers to be attached to a Durable Object from its exports entry

    A container can now be linked to its Durable Object from the export side, using a new container field that names an entry in the containers array. As a result containers[].class_name is now optional — a container that is referenced this way only needs a name:

    {
  "name": "my-worker",
  "main": "worker.js",
  "compatibility_date": "2026-07-01",
  "containers": [
    { "name": "my-container", "image": "./Dockerfile", "max_instances": 1 }
  ],
  "exports": {
    "MyContainerDO": {
      "type": "durable-object",
      "storage": "sqlite",
      "container": "my-container"
    }
  }
}

    The existing containers[].class_name direction keeps working and either direction may be used, but the two must agree: a container that names its Durable Object cannot also be claimed by a different one.

    container is only valid on live durable-object exports (created and expecting-transfer) and requires storage: "sqlite". Wrangler now also reports an error when:

    • a container reference names a container that does not exist
    • two Durable Object exports claim the same container
    • a container and a Durable Object export disagree about which one they are linked to
    • a container ends up linked to no Durable Object at all
    • two containers share a name
    • a container's class_name names a Durable Object whose storage is legacy-kv
    • two containers are attached to the same Durable Object

    That last case was previously accepted but could never work: workerd attaches a single container per Durable Object namespace, and in local development every container for a class builds into the same image tag, so one silently overwrote the other. If you have two containers on one class_name, give each its own Durable Object class.

Patch Changes

  • #​15238 3a4fc6b Thanks @​jamesopstad! - Honor access.dev when running Workers with @cloudflare/vite-plugin, so ctx.access.getIdentity() returns the configured identity.

  • #​15028 d4f441f Thanks @​harshmathurx! - Handle Worker-side request body cancellation without surfacing stream controller errors in local dev.

  • #​15185 1f79ace Thanks @​jamesopstad! - Use a fixed default compatibility date rather than the current date

    When no compatibility date was set, Wrangler, C3 and the Vitest pool all defaulted to the current date. workerd only accepts a compatibility date up to 7 days beyond its own release, so whenever a workerd release was delayed the default could get ahead of the runtime that had been installed, and local development would fail to start.

    The default is now fixed at the release date of the workerd version that ships with each release, which leaves a week of headroom and updates as workerd is upgraded. @cloudflare/vite-plugin previously inlined the date at which it was built. It now shares the same default.

  • #​15239 f431166 Thanks @​jamesopstad! - Prevent date-enabled Node.js compatibility from adding conflicting globals to generated runtime types

    Runtime type generation now treats Node.js compatibility enabled by a compatibility date the same way as an explicit nodejs_compat flag. Node.js globals continue to come from @types/node instead of being generated as any declarations that override those types.

  • #​15196 8fb2b87 Thanks @​skepticfx! - Use the FedRAMP High managed container registry when Wrangler targets the FedRAMP High compliance region

    Container builds, pushes, deployments, image commands, and local development now select the corresponding production or staging FedRAMP registry and API from either compliance_region or CLOUDFLARE_COMPLIANCE_REGION.

  • Updated dependencies [bc5726b, 1277a72, ba54f0d, 6529f0c, b7422b0, 186339c, 4f922dc, 4d74b8d, 2e0c962, 1f79ace, 49f73de, 7cee278, 8777180, 265256a, 1f79ace, f431166, 8fb2b87, 75cf407]:

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

v0.22.0

Compare Source

Minor Changes

  • #​13830 49d4e00 Thanks @​penalosa! - Mocking requests with MSW in Worker tests now requires MSW >= 2.14

    @cloudflare/vitest-pool-workers previously shipped internal shims to make MSW work inside the workerd runtime. MSW 2.14 added that support natively, so those shims have been removed.

    If you mock requests with MSW in your Worker tests, make sure you're on MSW >= 2.14; older versions will no longer intercept requests. You can keep using setupServer() from msw/node, or adopt the official @msw/cloudflare integration via setupNetwork(). See the updated request-mocking example fixture for the recommended pattern.

Patch Changes

  • #​15211 bc5726b Thanks @​nithin42! - Honor access.dev when running Workers with @cloudflare/vitest-pool-workers, so ctx.access.getIdentity() returns the configured identity just as it does with wrangler dev.

  • #​15156 3ddd3ce Thanks @​dario-piotrowicz! - Fix module resolution for relative require() inside CJS deps when the project path contains spaces

    When a project lives under a directory with a space in its name, externalized CommonJS dependencies that use relative require() calls (e.g. require("./lib/impl.js")) would fail with "No such module" because workerd preserves URL encoding in the module name. Encoded module paths are now handled deterministically before CommonJS resolution without altering literal percent sequences.

  • #​15150 2cf3143 Thanks @​kkkhs! - Restore typed inject() keys in cloudflareTest() pool options

    inject() inside cloudflareTest() options again infers the value type from the keys you declare in your Vitest ProvidedContext, and reports misspelled keys. For keys that are only provided at runtime, pass an explicit type argument, e.g. inject<number>("myPort").

  • #​15232 8777180 Thanks @​vicb! - Bump capnp-es to 0.0.16.

  • #​15185 1f79ace Thanks @​jamesopstad! - Use a fixed default compatibility date rather than the current date

    When no compatibility date was set, Wrangler, C3 and the Vitest pool all defaulted to the current date. workerd only accepts a compatibility date up to 7 days beyond its own release, so whenever a workerd release was delayed the default could get ahead of the runtime that had been installed, and local development would fail to start.

    The default is now fixed at the release date of the workerd version that ships with each release, which leaves a week of headroom and updates as workerd is upgraded. @cloudflare/vite-plugin previously inlined the date at which it was built. It now shares the same default.

  • Updated dependencies [bc5726b, 1277a72, ba54f0d, 6529f0c, b7422b0, 186339c, 4f922dc, 4d74b8d, 2e0c962, 1f79ace, 49f73de, 7cee278, 8777180, 265256a, 1f79ace, f431166, 8fb2b87, 75cf407]:

dubzzz/fast-check (@​fast-check/vitest)

v0.5.0

Support for plugins and for Vitest v5
[Code][Diff]

Features

  • (PR#7219) Support plugin API of fast-check
  • (PR#7244) Support Vitest 5
kobaltedev/kobalte (@​kobalte/core)

v0.13.14

Compare Source

Patch Changes

  • 3d32663: ## v0.13.14 (September 7, 2026)

    Bug fixes

    • Preserve aria-hidden during modal handoff (#​721)
    • Resolve interact-outside targets across shadow boundaries (#​722)
    • Combobox: Prevent filter reset on blur (#​731)
octokit/core.js (@​octokit/core)

v7.0.8

Compare Source

Bug Fixes
microsoft/playwright (@​playwright/test)

v1.63.0

Compare Source

🔒 Test locks

Tests that access a shared resource — an external service, a global account setting — can now declare a named lock.
Tests that share a lock name never run concurrently, across files, workers and projects, while
everything else keeps running in parallel:

test('update user settings', { lock: 'user-settings' }, async ({ page }) => {
  // never runs at the same time as other tests holding 'user-settings'
});

A test can hold multiple locks, and test.describe() accepts a lock for the whole grou

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • Between 12:00 AM and 08:59 AM, only on Monday (* 0-8 * * 1)
  • 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.

👻 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 has been generated by Mend Renovate CLI.

@khepri-bot
khepri-bot Bot requested a review from a team September 7, 2026 04:55
@khepri-bot khepri-bot Bot added the renovate label Sep 7, 2026
@khepri-bot
khepri-bot Bot force-pushed the renovate/all-non-major-dependencies branch 17 times, most recently from c723660 to 24731b6 Compare September 13, 2026 23:16
@khepri-bot
khepri-bot Bot force-pushed the renovate/all-non-major-dependencies branch 11 times, most recently from 115dddd to 97fd49c Compare September 18, 2026 04:54
@khepri-bot
khepri-bot Bot force-pushed the renovate/all-non-major-dependencies branch 19 times, most recently from baf899f to 12f0490 Compare September 29, 2026 22:25
@khepri-bot
khepri-bot Bot force-pushed the renovate/all-non-major-dependencies branch 9 times, most recently from 56fcd88 to ec54a9b Compare October 4, 2026 06:05
@khepri-bot
khepri-bot Bot force-pushed the renovate/all-non-major-dependencies branch from ec54a9b to 89669c4 Compare October 4, 2026 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants