blog · release

bunqueue v2.7.10

Fixes 1 bug and ships 1 addition. clean() left orphan rows in job_results table (Issue #84, follow-up from @jdorner), storage.deleteJob() executed only DELETE FROM jobs, so cleaned completed jobs' result rows persisted forever in…

egeominotti

To install bunqueue v2.7.10

bun add bunqueue@2.7.10

npm install bunqueue@2.7.10

To upgrade bunqueue

bun add bunqueue@latest

What’s new

• deleteJobResult prepared statement in src/infrastructure/persistence/statements.ts.

Bugfixes

• clean() left orphan rows in job_results table (Issue #84, follow-up from @jdorner), storage.deleteJob() executed only DELETE FROM jobs, so cleaned completed jobs’ result rows persisted forever in job_results. deleteJob() now runs both DELETE FROM jobs and DELETE FROM job_results WHERE job_id = ? inside a single db.transaction(...) block, atomically cascading the removal. DLQ is intentionally not cascaded here: moveFailedJobToDlq() relies on saveDlqEntry + deleteJob preserving the DLQ row. Callers that clean DLQ (e.g. cleanFailed) explicitly call deleteDlqEntry beforehand.

Tests

• 2 regression tests in test/client-queue-operations.test.ts: clean(‘completed’) leaves no orphan job_results rows; clean(‘failed’) leaves no orphan rows in jobs/dlq/job_results.
• Updated test/sqlite-serializer.test.ts statement count (13 → 14).

Thanks to 1 contributor!

• @egeominotti

---

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