chore(deps): update dependency @cloudflare/vitest-pool-workers to v0.18.4

[renovate-fullsend]

This PR contains the following updates:

Package	Change	Age	Confidence
@cloudflare/vitest-pool-workers (source)	0.18.0 → 0.18.4

---

Release Notes

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

v0.18.4

Compare Source

Patch Changes

• #​14535 1b965c5 Thanks @​Naapperas! - Support dynamic retry delays for Workflow steps in local dev

  A step's retries.delay can now be a function that computes the delay per failed attempt, in addition to a static duration. The function receives { ctx, error } and returns a delay (a number of milliseconds or a duration string like "30 seconds"), and its result is fed into the configured backoff.

  await step.do(
    "call flaky API",
    {
      retries: {
        limit: 5,
        backoff: "constant",
        delay: ({ ctx }) => ctx.attempt * 1000,
      },
    },
    async () => {
      /* ... */
    }
  );

  The function is invoked once per failed attempt with a 5 second timeout. If it throws, times out, or returns an invalid value, the step fails without further retries.

• Updated dependencies [0283a1f, 7b28392, 1b965c5]:

  • wrangler@​4.110.0
  • miniflare@​4.20260708.1

v0.18.3

Compare Source

Patch Changes

• #​14489 e3f0cd6 Thanks @​edmundhung! - Add listDurableObjectIds() to Miniflare

  Miniflare now exposes listDurableObjectIds() for listing persisted Durable Object instance IDs by binding name. The Vitest pool now uses this shared Miniflare API internally instead of duplicating Miniflare's storage listing logic.

• Updated dependencies [e3f0cd6, 8511ddf, 9f74a5f, e3f0cd6, c782e2a, 2fedb1f, 17d2fc1]:

  • miniflare@​4.20260708.0
  • wrangler@​4.109.0

v0.18.2

Compare Source

Patch Changes

• Updated dependencies [54f74b8, 0852346, 54f74b8]:
  • wrangler@​4.108.0
  • miniflare@​4.20260706.0

v0.18.1

Compare Source

Patch Changes

• #​14409 16fbf81 Thanks @​matingathani! - reset() from cloudflare:test now resets ratelimit binding state between tests. Previously, RATE_LIMITERS bindings retained their in-memory bucket counts across test boundaries, causing later tests in the same file to see stale rate-limit exhaustion state.

• Updated dependencies [e7e5780, d88555e, 5fd8bee, 5d9990e, bf49a41, 1ac96a1, f416dd9, 1ca8d8f, 16fbf81, b973ed3]:

  • miniflare@​4.20260702.0
  • wrangler@​4.107.1

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 10:33 AM UTC · Completed 10:40 AM UTC
Commit: 965a443 · View workflow run →

[fullsend-ai-retro]

Retro: PR #3453 — Renovate lockfile-only update for @cloudflare/vitest-pool-workers

What happened

PR #3453 was a Renovate bot lockfile-only update bumping @cloudflare/vitest-pool-workers from 0.18.0 to 0.18.4. CI failed on both the web and build jobs because npm ci reported @cloudflare/workers-types@5.20260710.1 was missing from the lock file. The root cause: vitest-pool-workers@0.18.4 pulls in wrangler@4.110.0, which has a peer dependency on @cloudflare/workers-types@^5.x, conflicting with the ^4.x range pinned in package.json. Renovate's lockfile-only strategy cannot fix this because a package.json change is required. Renovate force-pushed 4 times over 2 days (rebasing onto main) without detecting the persistent CI failure. A human (rh-hemartin) closed the PR on Jul 10 and manually created PR #4002 to bump @cloudflare/workers-types from v4 to v5.

Proposals

1. Group Cloudflare packages in Renovate config — Add a groupName rule for @cloudflare/vitest-pool-workers, @cloudflare/workers-types, and wrangler so they are updated together, preventing broken lockfile-only PRs when these tightly-coupled packages have cross-dependency version requirements.

Additional notes

This PR is also another instance of the retro-on-unmerged-bot-PR pattern already tracked in #3177 and #3951, with multiple evidence issues already filed (#3984, #3955). No new proposal is needed for that pattern.

Proposals filed

• Group Cloudflare packages in Renovate config to prevent broken lockfile-only PRs (in fullsend-ai/fullsend)