@adonis-agora/durable-dashboard 1.0.0-rc.0 → 1.0.0-rc.2

package/CHANGELOG.md

@@ -1,5 +1,35 @@
 # @adonis-agora/durable-dashboard
 
+## 1.0.0-rc.2
+
+### Patch Changes
+
+- [#495](https://github.com/DavideCarvalho/adonis-agora-durable/pull/495) [`ac19140`](https://github.com/DavideCarvalho/adonis-agora-durable/commit/ac1914059808a48d239fbb52dd9ce26b1d68e493) Thanks [@DavideCarvalho](https://github.com/DavideCarvalho)! - Console fixes found by a smoke test of the 1.0 console:
+  
+  - **Actions work under shield.** Every write the console sends (cancel, retry, update, signal, task, bulk, schedules) carries the `XSRF-TOKEN` cookie back as `x-xsrf-token`, and a write is never redirected silently: a refused request (a redirect, or any non-2xx answer) shows as an error on the page instead of looking like nothing happened.
+  - **The `window.__DURABLE_BASE__` / `__DURABLE_API__` overrides are gone.** The provider's JSON config block is the only source; without it the console uses `/durable` and `/durable/api`.
+  - **The run detail of a waiting run** carries what the run waits on (`run.waiting`, as list rows do), so "Send update", "Deliver signal" and the task actions show whatever page the list is on, and the header reads `awaiting` (or `suspended` for a run parked on nothing named) instead of `running`.
+  - **A `cancelling` run** reads "Cancelling" instead of falling through to "Saga compensated".
+  - **The status chips' counts (ALL included)** are recounted with every list refresh.
+  - The dashboard package no longer lists a README it does not ship.
+
+## 1.0.0-rc.1
+
+### Minor Changes
+
+- [#486](https://github.com/DavideCarvalho/adonis-agora-durable/pull/486) [`ab26861`](https://github.com/DavideCarvalho/adonis-agora-durable/commit/ab26861edb93aefad8aa949f32913b6d3681c519) Thanks [@DavideCarvalho](https://github.com/DavideCarvalho)! - A compensating cancel now persists a new run status, `cancelling`.
+  
+  `engine.cancel(runId, { compensate: true })` marks the run `cancelling` before it returns, and returns that status. The run keeps it while the saga's compensations run, then becomes `cancelled`. While it is `cancelling`:
+  
+  - A repeat `cancel()`, with or without `compensate`, returns `cancelling` and leaves the undo alone. Before, a second cancel without `compensate` marked the run `cancelled` and skipped the compensations still running.
+  - Crash recovery re-drives it on any instance, so an undo whose pod died is finished elsewhere.
+  - It keeps its singleton and concurrency slot, `waitForRun` keeps waiting, `engine.requeue()` returns it unchanged, and an `overlap: 'skip'` schedule doesn't fire over it.
+  - The dashboard and the API show it as its own status, with a filter chip.
+  
+  A failed write of the cancel request now fails `cancel()` instead of being ignored, and leaves the run as it was.
+  
+  **Breaking:** `RunStatus` has a new member, `cancelling`. Exhaustive `switch`es over `RunStatus` need a case for it. A custom `StateStore` must return `cancelling` runs from `listIncompleteRuns` and `listOrphanedRuns` (the new `RECOVERABLE_RUN_STATUSES` lists them, and the state-store conformance suite checks it), or recovery won't finish a crashed compensating cancel.
+
 ## 1.0.0-rc.0
 
 ### Major Changes