Skip to content
Get started
Get started
bunqueue v2.8.57
View Markdown
blog · release

bunqueue v2.8.57

Fixed an order-dependent CI failure caused by a Workflow production test leaving the process-wide embedded manager initialized in memory.

bun add bunqueue@2.8.57
npm install bunqueue@2.8.57
bun add bunqueue@latest
  • 2.8.56 is broken. Install 2.8.57 or newer. Its CI run was red — one unit test failed on embedded parent-dependency recovery across a broker restart — so the quality gate blocked the tag, release and image. Only the npm artifact exists, because it was pushed manually while the gate was failing. It is being deprecated on npm as part of this release, and unpublished as well if that happens inside npm’s 72-hour window.
  • Fixed an order-dependent CI failure caused by a Workflow production test leaving the process-wide embedded manager initialized in memory. Its teardown now pairs Engine.close() with shutdownManager(), preserving the documented shared-manager ownership contract while preventing the following durable parent restart test from using the wrong backend.
  • Added an offline consumer test for the exact npm tarball. It verifies the manifest exports and imports defineConfig from bunqueue, Queue and Worker from bunqueue/client, and Engine from bunqueue/workflow after packing the release. The consumer unpacks the archive into its own node_modules and links only the declared dependencies, proving croner and msgpackr are enough for every entrypoint. The CLI and runtime remain Bun-only by design.
  • Fixed the scheduled Go mutation job, which aborted before its first mutant because Bun was missing from PATH while the Go suite spawns a real broker.
  • Cleared the weekly SDK advisory gate by overriding the TypeScript SDK’s transitive qs@6.15.1 (GHSA-q8mj-m7cp-5q26) to a patched ^6.15.2. The override only affects the mutation toolchain; the published client has no qs dependency.

← bunqueue v2.8.56 · Release on GitHub · Commits since v2.8.55 · Full changelog · All posts