@zerotal/queue 1.7.2 → 1.7.4

package/CHANGELOG.md

@@ -8,6 +8,8 @@ follows the Zerotal monorepo's unified versioning.
 
 ## [Unreleased]
 
+## [1.7.2] — 2026-08-18
+
 ### Fixed
 
 - **`queue:work` listened on one hardcoded queue, so queued notifications were never sent.**
@@ -22,10 +24,9 @@ follows the Zerotal monorepo's unified versioning.
   `["default"]`. The flag still overrides it and now accepts a comma-separated list
   (`--queue=emails,reports`) in priority order, so one worker can take a subset without a second
   process. `--once` stops at the first queue with a claimable job rather than taking one job per
-  queue, and the idle sleep is only taken when *no* queue had anything — sleeping after the first
+  queue, and the idle sleep is only taken when _no_ queue had anything — sleeping after the first
   empty one would leave a busy second queue waiting out the poll interval.
 
-
 ## [1.5.0] — 2026-08-15
 
 ### Added

package/api-surface.md

@@ -298,13 +298,13 @@ interface WorkerPoolOptions = {
   size: number
 }
 
-type BatchStatus = 'failed' | 'pending' | 'complete'
+type BatchStatus = 'pending' | 'complete' | 'failed'
 
 type JobStatus = 'dispatched' | 'completed' | 'failed' | 'retried'
 
 type SerializedJob = {    className: string;    payload: Record<string, unknown>;}
 
-type WorkerResult = {    success: true;} | {    success: false;    error: string;}
+type WorkerResult = { success: true } | { success: false; error: string }
 
 ## ./commands  `(./src/commands/index.ts)`
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zerotal/queue",
-  "version": "1.7.2",
+  "version": "1.7.4",
   "license": "MIT",
   "maturity": "stable",
   "private": false,
@@ -31,8 +31,8 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@zerotal/core": "1.7.2",
-    "@zerotal/orm": "1.7.2"
+    "@zerotal/core": "1.7.4",
+    "@zerotal/orm": "1.7.4"
   },
   "devDependencies": {
     "typescript": "^5.8.0"