@geonosis/workflows 0.3.0 → 0.3.1

package/CHANGELOG.md

@@ -0,0 +1,43 @@
+# @geonosis/workflows
+
+## 0.3.1
+
+### Patch Changes
+
+- d15a654: **A bump names what the floors it crossed changed, and runs the tier it left behind (#268).** The
+  `BY HAND` block was driven by the doctor's required-option FAILs alone, so `--floors latest` across
+  a floor minor that changed `sessionDb`'s key printed nothing and the consumer's own tests found it.
+  `update` now reads each bumped floor's own `CHANGELOG.md` out of what the install unpacked, for the
+  versions crossed, and prints every change its author named — and says so by name when a floor ships
+  no changelog to read (measured: `npm pack --dry-run --json` over a floor carries `dist`,
+  `package.json`, `README.md` and `LICENSE`; CHANGELOG is not on npm's always-included list, so the
+  floors name it in `files` now). A seventh ritual step runs the tier this tree calls `fast` in
+  `geonosis.json` after the frozen install: a bump cannot report PASS over a tree it has just
+  reddened, and a repo that declares no tier is told so rather than passed over.
+- Updated dependencies [d15a654]
+  - @geonosis/conformance@0.2.1
+  - @geonosis/events@1.5.2
+
+## 0.3.0
+
+### Minor Changes
+
+- 13ca75b: **Every conformance case that can name its refusal now names it (#213).** `assertRefuses` takes the class or a phrase of the refusal, and five cases were still passing nothing: an index that refused an undeclared filter, value or ordering with any error at all passed the search exam, and a journal that refused a held idempotency key with a raw uniqueness violation passed two of the three cases about it. The search cases require `SearchRefusal` and the journal cases `IdempotencyKeyHeldError` — the classes both contracts already export for exactly this. A subject that refuses with something else now fails, naming what it threw.
+
+### Patch Changes
+
+- Updated dependencies [e0da9a3]
+  - @geonosis/events@1.5.1
+
+## 0.2.0
+
+### Minor Changes
+
+- 6b5b3db: **BREAKING for a durable workflow: the definition declares its execution, and each door refuses the other's (#210).** `createWorkflow` hardcoded `execution: 'inline'` and `WorkflowOptions` had no way to say otherwise, while `durable-body-reads-through-steps` read a `durable`/`execution` key off the call — a declaration a consumer could not write without an excess-property error, so the engine and its own rule disagreed about what a durable workflow looks like. `WorkflowOptions.execution` (default `'inline'`) is carried on the definition; `executeDurable` refuses a workflow declared inline and `.run()` refuses one declared durable, both by name — a body written for one request is replayed by the durable door, and that is exactly the free read the rule exists for. **REACH CHANGED:** the rule's defaults are now `durableKey: 'execution'`, `durableValue: 'durable'`, the engine's own spelling; a repo whose factory says it another way names `durableKey`/`durableValue`. A durable workflow must add `{ execution: 'durable' }`.
+
+### Patch Changes
+
+- Updated dependencies [bb5e84b]
+- Updated dependencies [6d14aa2]
+  - @geonosis/conformance@0.2.0
+  - @geonosis/events@1.5.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@geonosis/workflows",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "types": "./dist/index.d.ts",
   "description": "A workflow engine with one door: named steps whose compensation travels with them, a body that is a real async function with real values, and a journal contract whose run lifecycle, transactional outbox and reverse-start unwinding are model-checked.",
   "keywords": [
@@ -33,11 +33,12 @@
     }
   },
   "files": [
+    "CHANGELOG.md",
     "dist"
   ],
   "dependencies": {
-    "@geonosis/conformance": "^0.2.0",
-    "@geonosis/events": "^1.5.1"
+    "@geonosis/conformance": "^0.2.1",
+    "@geonosis/events": "^1.5.2"
   },
   "engines": {
     "node": ">=22"