@sapiom/orchestration 0.1.3 → 0.1.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/CHANGELOG.md +13 -0
  2. package/package.json +2 -2
package/CHANGELOG.md CHANGED
@@ -1,5 +1,18 @@
1
1
  # @sapiom/orchestration
2
2
 
3
+ ## 0.1.4
4
+
5
+ ### Patch Changes
6
+
7
+ - 2f957ca: Depend on `@sapiom/tools` with a caret range (`^0.1`) instead of an exact
8
+ version. The dependency was declared `workspace:*`, which publishes as the exact
9
+ resolved version — so `@sapiom/orchestration@0.1.2` carried a hard `0.1.2` pin and
10
+ forced a second copy of `@sapiom/tools` whenever a project used a newer patch
11
+ (e.g. tools `0.1.3`), producing duplicate nominal types and `tsc` errors. A caret
12
+ range lets the consumer's own `@sapiom/tools` (any `0.1.x`) satisfy and dedupe to
13
+ a single copy, while still pulling tools in transitively so authoring types
14
+ resolve out of the box.
15
+
3
16
  ## 0.1.3
4
17
 
5
18
  ### Patch Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sapiom/orchestration",
3
- "version": "0.1.3",
3
+ "version": "0.1.4",
4
4
  "description": "Versioned public contract for authoring Sapiom orchestrations: types, directive constructors/guards, defineOrchestration, defineStep, InMemoryContextStore. Shared by customer orchestration definitions, the sandbox step-runner, and the engine.",
5
5
  "license": "MIT",
6
6
  "author": "Sapiom",
@@ -34,7 +34,7 @@
34
34
  ],
35
35
  "sideEffects": false,
36
36
  "dependencies": {
37
- "@sapiom/tools": "0.1.3"
37
+ "@sapiom/tools": "^0.1.3"
38
38
  },
39
39
  "peerDependencies": {
40
40
  "zod": "^3.25.76"