@warlock.js/scheduler 5.25.0 → 5.26.0

package/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to `@warlock.js/scheduler` are documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). `@warlock.js/*` packages are released in lockstep — every package shares the same version number, so a version below may list only the changes that affected this package.
 
+## 5.26.0 - 2026-09-30
+
+### Changed
+
+- Lockstep release; package APIs are unchanged.
+
 ## 5.25.0 - 2026-09-28
 
 ### Changed

package/llms-full.txt

@@ -877,6 +877,17 @@ process.on("SIGTERM", async () => {
 
 > Registering jobs alone runs nothing — you must call `scheduler.start()`. As a safety net, in development (`NODE_ENV !== "production"`) the scheduler logs a one-shot `console.warn` if jobs are registered but `start()` is never called.
 
+## Run scheduled jobs inside a context
+
+Use `scheduler.around(hook)` to wrap every callback execution — each retry attempt too — for example in an `AsyncLocalStorage` context:
+
+```ts
+scheduler.around((job, run) => storage.run({ job: job.name }, run));
+```
+
+- First registered hook is the outermost; `around` returns an unsubscribe function.
+- A hook that never calls `run` skips the execution (`job:skip`, `result.skipped`); a hook that throws is treated as a callback error (retry/error path applies).
+
 ## Pick a skill
 
 | If the task is about… | Load |

package/package.json

@@ -8,7 +8,7 @@
     "dayjs": "^1.11.19"
   },
   "peerDependencies": {
-    "@warlock.js/cache": "5.25.0"
+    "@warlock.js/cache": "5.26.0"
   },
   "peerDependenciesMeta": {
     "@warlock.js/cache": {
@@ -33,7 +33,7 @@
   ],
   "author": "hassanzohdy",
   "license": "MIT",
-  "version": "5.25.0",
+  "version": "5.26.0",
   "main": "./cjs/index.cjs",
   "module": "./esm/index.mjs",
   "types": "./esm/index.d.mts",