Skip to content

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

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/all-minor-patch
Open

fix(deps): update all non-major dependencies#50
renovate[bot] wants to merge 1 commit intomainfrom
renovate/all-minor-patch

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 9, 2026 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change OpenSSF
@cloudflare/vitest-pool-workers (source) devDependencies minor ^0.12.0 → ^0.15.0 OpenSSF Scorecard
@cloudflare/workers-types devDependencies minor 4.20260228.0 → 4.20260426.1 OpenSSF Scorecard
@eslint/js (source) devDependencies patch 9.39.3 → 9.39.4 OpenSSF Scorecard
@opentelemetry/api-logs (source) dependencies minor ^0.212.0 → ^0.215.0 OpenSSF Scorecard
@opentelemetry/otlp-transformer (source) dependencies minor ^0.212.0 → ^0.215.0 OpenSSF Scorecard
@sentry/cloudflare (source) dependencies minor 10.39.0 → 10.50.0 OpenSSF Scorecard
@types/node (source) devDependencies minor 24.10.13 → 24.12.2 OpenSSF Scorecard
@typescript-eslint/eslint-plugin (source) devDependencies minor 8.56.0 → 8.59.1 OpenSSF Scorecard
@typescript-eslint/parser (source) devDependencies minor 8.56.0 → 8.59.1 OpenSSF Scorecard
eslint (source) devDependencies patch 9.39.3 → 9.39.4 OpenSSF Scorecard
hono (source) dependencies patch 4.12.1 → 4.12.15 OpenSSF Scorecard
prettier (source) devDependencies patch 3.8.1 → 3.8.3 OpenSSF Scorecard
typescript-eslint (source) devDependencies minor 8.56.0 → 8.59.1 OpenSSF Scorecard
wrangler (source) devDependencies minor 4.67.0 → 4.86.0 OpenSSF Scorecard

Release Notes

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

v0.15.1

Compare Source

Patch Changes

v0.15.0

Compare Source

Minor Changes

  • #​13623 b156b2e Thanks @​penalosa! - Add reset() and abortAllDurableObjects() helpers to cloudflare:test

    The reset() helper deletes all data from attached bindings, and resets all Durable Object instances. This is useful for resetting state between test blocks.

    The abortAllDurableObjects() helper resets all Durable Object instances without deleting persisted data.

    import { reset } from "cloudflare:test";
import { afterEach } from "vitest";

afterEach(async () => {
  await reset();
});
Patch Changes

v0.14.9

Compare Source

Patch Changes

v0.14.8

Compare Source

Patch Changes

  • #​13548 1aee990 Thanks @​emily-shen! - Update warning message when attempting to access exports not defined on the main worker

    Previously this referred to the SELF worker, which is now a deprecated API in the Vitest integration.

  • #​13607 d5d0446 Thanks @​petebacondarwin! - fix: Restore workflow binding before async cleanup in WorkflowIntrospectorHandle.dispose()

    Previously, dispose() awaited all instance abort operations before restoring the original env binding. On slower CI environments (especially Windows), this left a window where the next test could see a stale proxy, causing "Trying to mock step multiple times" errors or failed introspection. The binding is now restored synchronously before the async instance cleanup begins.

  • #​13007 2c3258d Thanks @​sheplu! - Reduce default log verbosity from VERBOSE to INFO

    The pool logger was previously hardcoded to VERBOSE, causing noisy debug messages on every test run (e.g. [vpw:debug] Adding compatibility flag...). Only informational, warning, and error messages are now printed by default.

    For debugging, set NODE_DEBUG=vitest-pool-workers to restore the detailed output.

  • Updated dependencies [05f4443, 4a9ba90, d8c895a, b35617b, 7dc0433, 8ca78bb, b6e1351, d8314c6, b35617b, 7f50300, 4fda685, be5e6a0, e456952, 59eec63, 50bf819, cc1413a, d0a9d1c, 4eb1da9, 8ca78bb, 266c418, 6d887db, 5716d69]:

    • wrangler@​4.84.0
    • miniflare@​4.20260420.0

v0.14.7

Compare Source

Patch Changes

v0.14.6

Compare Source

Patch Changes
  • Updated dependencies [9b2b6ba]:
    • wrangler@​4.82.2

v0.14.5

Compare Source

Patch Changes

v0.14.4

Compare Source

Patch Changes

v0.14.3

Compare Source

Patch Changes

v0.14.2

Compare Source

Patch Changes

  • #​13095 65e6684 Thanks @​penalosa! - Reject V8 coverage provider with a clear error message

    V8 native code coverage (@vitest/coverage-v8) requires node:inspector to collect profiling data from V8's runtime. workerd only provides node:inspector as a non-functional stub, so V8 coverage would silently fail or crash with a confusing No such module "node:inspector" error.

    The pool now detects this configuration early — during Vite plugin setup, before Vitest tries to load the coverage provider — and throws a clear error directing users to use Istanbul coverage instead, which works by instrumenting source code at build time and runs on any JavaScript runtime.

  • Updated dependencies [a3e3b57, 7d318e1, fa6d84f, 96ee5d4, 7d318e1, 7a60d4b, 78cbe37, 6fa5dfd]:

    • miniflare@​4.20260405.0
    • wrangler@​4.81.0

v0.14.1

Compare Source

Patch Changes

  • #​13131 65acf66 Thanks @​dario-piotrowicz! - Use miniflare's handleStructuredLogs option instead of handleRuntimeStdio for processing workerd output

    Previously, vitest-pool-workers manually processed raw stdout/stderr streams from the workerd runtime via handleRuntimeStdio, with its own filtering of known noisy messages (e.g. LLVM symbolizer warnings). This switches to miniflare's handleStructuredLogs option, which parses workerd's structured JSON log output and automatically filters known unhelpful messages. This aligns with how both wrangler and vite-plugin-cloudflare handle workerd logs.

  • Updated dependencies [9c4035b, 5d29055, fb67a18, d5bffde, ab44870, 48d83ca, b2f53ea, b9b7e9d, 14e72eb, 4dc94fd, b2f53ea, d5bffde, 48d83ca]:

    • wrangler@​4.80.0
    • miniflare@​4.20260401.0

v0.14.0

Compare Source

Minor Changes

  • #​12858 f05f2da Thanks @​repository! - Add disableRetryDelays() to WorkflowInstanceModifier to skip retry backoff delays in tests

    When testing Workflows with retry configurations, the backoff delays between retry attempts of a failing step.do() caused real wall-clock waiting (e.g., 35 seconds for 3 retries with 5-second exponential backoff), even when step results were fully mocked. The new disableRetryDelays() method eliminates these delays while preserving retry behavior — all attempts still execute, just without waiting between them.

Patch Changes

  • #​13091 6d58f0f Thanks @​penalosa! - Use today's date for the RTTI compat date query instead of a hardcoded "2023-12-01", so newly added Node.js builtin modules are recognized by the module fallback service.

  • #​13070 cdb9c88 Thanks @​penalosa! - Suppress CODE_MOVED for unknown code block log spam from workerd

    These are internal workerd diagnostic messages not relevant to application developers. Miniflare's structured log handler already filters them, but vitest-pool-workers uses a custom handleRuntimeStdio that bypasses that pipeline. This adds the pattern to the pool's own ignore list.

  • #​13069 6d0e329 Thanks @​penalosa! - fix: suppress outputGateBroken stderr noise when testing Workflows

  • #​13075 b8df076 Thanks @​penalosa! - Support @voidzero-dev/vite-plus-test as an alternative to vitest

    Users running tests via Vite+ (@voidzero-dev/vite-plus-test) with the recommended pnpm overrides no longer hit spurious version warnings or Disallowed operation called within global scope errors.

  • Updated dependencies [ffbc268, 9eff028, ed20a9b, f214760, 746858a, 9aad27f, 1fc5518, b539dc7, 9282493, a532eea, cd0e971, d4c6158, 2565b1d]:

    • wrangler@​4.79.0
    • miniflare@​4.20260329.0

v0.13.5

Compare Source

Patch Changes

  • #​13077 11c77b7 Thanks @​penalosa! - fix: runInDurableObject now correctly returns redirect responses (3xx) from Durable Object callbacks instead of throwing "Expected callback for X" errors

  • #​13056 8384743 Thanks @​penalosa! - fix: Support dynamic import() inside entrypoint and Durable Object handlers

    Previously, calling exports.default.fetch() or SELF.fetch() on a worker whose handler used a dynamic import() would hang and fail with "Cannot perform I/O on behalf of a different Durable Object". This happened because the module runner's transport — which communicates over a WebSocket owned by the runner Durable Object — was invoked from a different DO context.

    The fix patches the module runner's transport via the onModuleRunner hook so that all invoke() calls are routed through the runner DO's I/O context, regardless of where the import() originates.

  • #​13074 4618c05 Thanks @​penalosa! - fix: only apply module fallback extension probing for require(), not import

    The module fallback service previously tried adding .js, .mjs, .cjs, and .json suffixes to extensionless specifiers unconditionally. Per the Node.js spec, this extension-probing behaviour is specific to CommonJS require(). ESM import statements must include explicit file extensions.

    Extension-less TypeScript import specifiers continue to work correctly — they are resolved by Vite's resolver rather than the fallback's extension loop.

  • #​13073 baec845 Thanks @​penalosa! - Add adminSecretsStore() to cloudflare:test for seeding secrets in tests

    Secrets store bindings only expose a read-only .get() method, so there was previously no way to seed secret values from within a test. The new adminSecretsStore() helper returns Miniflare's admin API for a secrets store binding, giving tests full control over create, update, and delete operations.

    import { adminSecretsStore } from "cloudflare:test";
import { env } from "cloudflare:workers";

const admin = adminSecretsStore(env.MY_SECRET);
await admin.create("test-value");

const value = await env.MY_SECRET.get(); // "test-value"

  • #​13083 cfd513f Thanks @​penalosa! - Add a 30-second timeout to waitUntil promise draining to prevent hanging tests

    Previously, if a ctx.waitUntil() promise never resolved, the test suite would hang indefinitely after the test file finished. Now, any waitUntil promises that haven't settled within 30 seconds are abandoned with a warning, allowing the test suite to continue. This aligns with the production waitUntil limit.

  • Updated dependencies [eeaa473, 9fcdfca, bc24ec8, 1faff35, 0b4c21a, 535582d, 992f9a3, f4ea4ac, 91b7f73, f6cdab2, 53ed15a, ce65246, 7a5be20, 6b50bfa, 0386553, 9c5ebf5, 53ed15a, 53ed15a]:

    • wrangler@​4.78.0
    • miniflare@​4.20260317.3

v0.13.4

Compare Source

Patch Changes

v0.13.3

Compare Source

Patch Changes

v0.13.2

Compare Source

Patch Changes

v0.13.1

Compare Source

Patch Changes

v0.13.0

Compare Source

Minor Changes

  • #​11632 a6ddbdb Thanks @​penalosa! - Support Vitest 4 in @cloudflare/vitest-pool-workers.

    This a breaking change to the @cloudflare/vitest-pool-workers integration in order to support Vitest v4. Along with supporting Vitest v4 (and dropping support for Vitest v2 and v3), we've made a number of changes that may require changes to your tests. Our aim has been to improve stability & the foundations of @cloudflare/vitest-pool-workers as we move towards a v1 release of the package.

    We've made a codemod to make the migration easier, which will make the required changes to your config file:

    npx jscodeshift -t node_modules/@​cloudflare/vitest-pool-workers/dist/codemods/vitest-v3-to-v4.mjs vitest.config.ts

    Or, without installing the package first:

    npx jscodeshift -t https://unpkg.com/@​cloudflare/vitest-pool-workers/dist/codemods/vitest-v3-to-v4.mjs --parser=ts vitest.config.ts

    • Config API: defineWorkersProject and defineWorkersConfig from @cloudflare/vitest-pool-workers/config have been replaced with a cloudflareTest() Vite plugin exported from @cloudflare/vitest-pool-workers. The test.poolOptions.workers options are now passed directly to cloudflareTest():

      Before:

      import { defineWorkersProject } from "@​cloudflare/vitest-pool-workers/config";

export default defineWorkersProject({
  test: {
    poolOptions: {
      workers: {
        wrangler: { configPath: "./wrangler.jsonc" },
      },
    },
  },
});

      After:

      import { cloudflareTest } from "@​cloudflare/vitest-pool-workers";
import { defineConfig } from "vitest/config";

export default defineConfig({
  plugins: [
    cloudflareTest({
      wrangler: { configPath: "./wrangler.jsonc" },
    }),
  ],
});

    • isolatedStorage & singleWorker: These have been removed in favour of a simpler isolation model that more closely matches Vitest. Storage isolation is now on a per test file basis, and you can make your test files share the same storage by using the Vitest flags --max-workers=1 --no-isolate

    • import { env, SELF } from "cloudflare:test": These have been removed in favour of import { env, exports } from "cloudflare:workers". exports.default.fetch() has the same behaviour as SELF.fetch(), except that it doesn't expose Assets. To test your assets, write an integration test using startDevWorker()

    • import { fetchMock } from "cloudflare:test": This has been removed. Instead, mock globalThis.fetch or use ecosystem libraries like MSW (recommended).

    • Vitest peer dependency: @cloudflare/vitest-pool-workers now requires vitest@^4.1.0.

Patch Changes

v0.12.21

Compare Source

Patch Changes

v0.12.20

Compare Source

Patch Changes
  • Updated dependencies [ec2459e]:
    • wrangler@​4.71.0
    • miniflare@​4.20260301.1

v0.12.19

Compare Source

Patch Changes

v0.12.18

Compare Source

Patch Changes

v0.12.17

Compare Source

Patch Changes
  • Updated dependencies [3d6e421, 294297e]:
    • wrangler@​4.68.1
    • miniflare@​4.20260302.0

v0.12.16

Compare Source

Patch Changes

v0.12.15

Compare Source

Patch Changes

  • #​12602 58a4020 Thanks @​anonrig! - Optimize filesystem operations by using Node.js's throwIfNoEntry: false option

    This reduces the number of system calls made when checking for file existence by avoiding the overhead of throwing and catching errors for missing paths. This is an internal performance optimization with

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)

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

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented Mar 9, 2026 •
edited
Loading

Deploying duyet-logs with  Cloudflare Pages  Cloudflare Pages

Latest commit: a5d9f48
Status:🚫  Build failed.

View logs

@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from bb09805 to 533ef46 Compare March 13, 2026 11:00
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Mar 13, 2026 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: duyet-logs@1.0.0
npm error Found: vitest@3.2.4
npm error node_modules/vitest
npm error   dev vitest@"^3.0.0" from the root project
npm error   peer vitest@"3.2.4" from @vitest/browser@3.2.4
npm error   node_modules/@vitest/browser
npm error     peerOptional @vitest/browser@"3.2.4" from vitest@3.2.4
npm error   1 more (@vitest/ui)
npm error
npm error Could not resolve dependency:
npm error peer vitest@"^4.1.0" from @cloudflare/vitest-pool-workers@0.15.1
npm error node_modules/@cloudflare/vitest-pool-workers
npm error   dev @cloudflare/vitest-pool-workers@"^0.15.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-28T15_03_56_248Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-28T15_03_56_248Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 371b282 to 439623e Compare March 31, 2026 15:04
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch from 439623e to c40dacc Compare April 6, 2026 02:01
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch from c40dacc to b4fda3f Compare April 17, 2026 16:10
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch from b4fda3f to a5d9f48 Compare April 24, 2026 11:15
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

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants