@walkeros/cli 2.2.0-next-1772811722420 → 3.0.0-next-1773236214827

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.
package/CHANGELOG.md CHANGED
@@ -1,27 +1,96 @@
1
1
  # @walkeros/cli
2
2
 
3
- ## 2.2.0-next-1772811722420
3
+ ## 3.0.0-next-1773236214827
4
+
5
+ ### Major Changes
6
+
7
+ - d11f574: Rename Flow.Setup to Flow.Config and Flow.Config to Flow.Settings for
8
+ consistent Config/Settings naming convention at every level. Breaking change:
9
+ all type names, function names, schema names, and API URL paths (/configs →
10
+ /settings) updated.
11
+ - 23f218a: Replace flat/v2 contract format with named contracts supporting
12
+ extends inheritance.
13
+
14
+ BREAKING CHANGES:
15
+ - `contract` is now a map of named contract entries (e.g.,
16
+ `{ "default": { ... }, "web": { ... } }`)
17
+ - `version` field inside contracts removed
18
+ - `$tagging` renamed to `tagging`
19
+ - Legacy flat contract format removed
20
+ - `$globals`, `$context`, `$custom`, `$user`, `$consent` references removed
21
+ - Settings-level `contract` field removed (use named contracts at config
22
+ level)
23
+ - Auto-injection of `$tagging` into `collector.tagging` removed (use
24
+ `$contract.name.tagging` explicitly)
25
+ - Validator `contract` setting renamed to `events` (receives raw schemas, not
26
+ `{ schema: ... }` wrappers)
27
+
28
+ NEW FEATURES:
29
+ - Named contracts with `extends` for inheritance (additive merge)
30
+ - Generalized dot-path resolution: `$def.name.nested.path`,
31
+ `$contract.name.section`
32
+ - `$contract` as first-class reference type with path access
33
+ - `$def` inside contracts supported via two-pass resolution
34
+ - `$def` aliasing for reducing repetition: `{ "c": "$contract.web" }` then
35
+ `$def.c.events`
36
+
37
+ - d5af3cf: Unified CLI and Docker runner into single `walkeros run` code path
38
+ with built-in health server, heartbeat, polling, and secrets support. Added
39
+ `--flow-id` and `--project` flags. Removed legacy `--deploy`, `--url`,
40
+ `--health-endpoint`, `--heartbeat-interval`, and `-h/--host` flags.
4
41
 
5
42
  ### Minor Changes
6
43
 
7
- - b6c8fa8: Add stores as a first-class component type in Flow.Setup. Stores get
8
- their own `stores` section in flow config, a `collector.stores` registry, and
9
- `$store:storeId` env wiring in the bundler. Includes `storeMemoryInit` for
10
- Flow.Setup compatibility and type widening in cache/file transformers.
44
+ - 6ae0ee3: Add v2 structured contract format with globals, context, custom,
45
+ user, and consent sections.
46
+
47
+ Contracts can now describe cross-event properties (globals, consent, etc.)
48
+ alongside entity-action event schemas. Top-level sections are JSON Schemas
49
+ that merge additively into per-event validation.
50
+
51
+ Breaking: None. Legacy flat contracts continue working unchanged. v2 is opt-in
52
+ via `version: 2` field.
53
+
54
+ - b6c8fa8: Add stores as a first-class component type in Flow.Config. Stores get
55
+ their own `stores` section in flow settings, a `collector.stores` registry,
56
+ and `$store:storeId` env wiring in the bundler. Includes `storeMemoryInit` for
57
+ Flow.Config compatibility and type widening in cache/file transformers.
11
58
 
12
59
  ### Patch Changes
13
60
 
61
+ - 2b259b6: Fix deterministic package version resolution in bundler.
62
+ - Two-phase resolve-then-install prevents version overwrites
63
+ - peerDependencies resolved at lowest priority (not equal to deps)
64
+ - Per-build temp directories prevent cross-build interference
65
+ - Optional peerDeps (peerDependenciesMeta) correctly skipped
66
+ - Prerelease versions handled with includePrerelease flag
67
+ - Package names validated against npm naming rules
68
+
14
69
  - ddd6a21: Generated Dockerfiles now include COPY lines for `include` folders,
15
70
  enabling fs store support in Docker containers.
16
71
  - 67dd7c8: Standardize command pattern: all three commands (validate, simulate,
17
72
  push) now route through their programmatic APIs for string resolution and
18
73
  orchestration. Extract shared createCollectorLoggerConfig utility. Pass
19
74
  missing silent/step options through simulate() API.
75
+ - 499e27a: Add sideEffects declarations to all packages for bundler tree-shaking
76
+ support.
77
+ - 55ce33e: Fix $store: forward reference bug in bundler codegen — stores are now
78
+ hoisted into a separate variable declaration before the config object,
79
+ ensuring store references resolve correctly at runtime
80
+ - Updated dependencies [2b259b6]
81
+ - Updated dependencies [2614014]
82
+ - Updated dependencies [6ae0ee3]
20
83
  - Updated dependencies [37299a9]
84
+ - Updated dependencies [499e27a]
85
+ - Updated dependencies [d11f574]
86
+ - Updated dependencies [d11f574]
87
+ - Updated dependencies [1fe337a]
88
+ - Updated dependencies [23f218a]
89
+ - Updated dependencies [499e27a]
21
90
  - Updated dependencies [c83d909]
22
91
  - Updated dependencies [b6c8fa8]
23
- - @walkeros/core@2.2.0-next-1772811722420
24
- - @walkeros/server-core@2.2.0-next-1772811722420
92
+ - @walkeros/core@3.0.0-next-1773236214827
93
+ - @walkeros/server-core@3.0.0-next-1773236214827
25
94
 
26
95
  ## 2.1.1
27
96
 
package/README.md CHANGED
@@ -231,7 +231,7 @@ Validate flow configurations, events, mappings, or contracts.
231
231
  walkeros validate <config-file> [options]
232
232
  ```
233
233
 
234
- By default, validates a Flow.Setup file — checking schema, references, and
234
+ By default, validates a Flow.Config file — checking schema, references, and
235
235
  cross-step example compatibility.
236
236
 
237
237
  **Options:**
@@ -339,7 +339,7 @@ walkeros bundle flow.json --no-cache
339
339
 
340
340
  ## Flow Configuration
341
341
 
342
- Flow configs use the `Flow.Setup` format with `version` and `flows`:
342
+ Flow configs use the `Flow.Config` format with `version` and `flows`:
343
343
 
344
344
  ```json
345
345
  {