@adonis-agora/durable 0.39.0 → 0.40.0

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # @adonis-agora/durable
 
+## 0.40.0
+
+### Minor Changes
+
+- [`b62ce42`](https://github.com/DavideCarvalho/adonis-agora-durable/commit/b62ce428e6262cf78f55ac96ef1433a3197c1878) Thanks [@DavideCarvalho](https://github.com/DavideCarvalho)! - Require cron-parser 5
+  
+  The optional `cron-parser` peer narrows from `^4.0.0 || ^5.0.0` to `^5.0.0`, and the
+  scheduler no longer recognises v4's `parseExpression` entry point — an unsupported major
+  now fails at load with a message naming the version it wants, rather than resolving to a
+  parser this code no longer drives correctly.
+  
+  Only projects that schedule workflows by cron are affected, and only those still on
+  cron-parser 4: install cron-parser 5. Nothing about cron expressions, timezones or fire
+  times changes; the scheduler computed identical fires under both majors, which is what
+  the compatibility suite asserted before this.
+
+## 0.39.1
+
+### Patch Changes
+
+- [#168](https://github.com/DavideCarvalho/adonis-agora-durable/pull/168) [`eb7e642`](https://github.com/DavideCarvalho/adonis-agora-durable/commit/eb7e642f0e956b00b0c177d34f30cb5747389f49) Thanks [@DavideCarvalho](https://github.com/DavideCarvalho)! - A failing lease release no longer escapes the turn's `finally`.
+  
+  The `finally` that ends a turn releases the recovery lease — including on the failure path, where the thing that failed the run is frequently the same store the release has to talk to. A step that violates a DB constraint leaves Postgres refusing every further statement on that connection, so the release throws out of the `finally`, and in a turn driven as a background resume that surfaces as an unhandled rejection rather than a failed run.
+  
+  Now swallowed and warned, by the same argument `releaseInflightLocks` already makes: a lease is a lease. It expires, and `recoverIncomplete` re-drives whatever is still held. A lost release costs one lease window of latency; an escaping one costs the diagnosis.
+  
+  Found in an application whose test deliberately violates NOT NULL inside the persist transaction to prove the workflow ends in `error`. Every assertion passed and the suite still exited non-zero, with a lease UPDATE as the only clue.
+
 ## 0.39.0
 
 ### Minor Changes