@walkeros/cli 4.7.0-next-1790187973605 → 4.7.0-next-1790722899482

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,51 +1,102 @@
1
1
  # @walkeros/cli
2
2
 
3
- ## 4.7.0-next-1790187973605
3
+ ## 4.7.0-next-1790722899482
4
4
 
5
5
  ### Minor Changes
6
6
 
7
- - ef02916: The `findExample` and `compareOutput` exports and the
8
- `ExampleLookupResult` type were removed from `@walkeros/cli`.
9
- - f5a1cfd: `walkeros validate` now reports unknown route targets as
10
- `UNKNOWN_ROUTE_TARGET` errors and warns about entries after an unconditional
11
- `stop` and about arrays that only pick the first match.
12
- `walkeros push --simulate collector.default` runs enrichment plus
13
- `collector.next`, `--mock collector.next.<id>` mocks one of its steps, and
14
- simulating a transformer now continues through its `next`.
15
- - ef02916: `walkeros validate` now reports a file path that does not exist or
16
- does not contain valid JSON as an input error with exit code 3, instead of
17
- validating the path string and failing the schema with exit code 1. Cross-step
18
- example checks now include an object `out`, such as a source example that
19
- produces a single walkerOS event, so incompatible connections are reported as
20
- errors.
7
+ - 06b498a: `walkeros bundle --manifest <url|path>` builds every artifact a build
8
+ manifest lists and uploads each one with a result. Declare build values in
9
+ `config.bundle.env`; they must be literal strings and supply `$env` in web
10
+ bundles. Step packages, overrides and their dependencies must now come from
11
+ the npm registry: git, file and URL specs are rejected.
12
+ - 74821ed: The canonical `flow-complete.json` example is rewritten as one tested
13
+ ecommerce setup with web, server and warehouse flows and a 15-chapter guide.
14
+ The new `flowCompleteManifest` export from `@walkeros/cli/examples` names
15
+ every feature by a stable id with a JSON Pointer into the file, so docs and
16
+ tools can reference it.
17
+ - 06b498a: `walkeros run` is removed. Build with `walkeros bundle`, then start
18
+ the artifact with `runneros start dist/flow.mjs` from the new
19
+ `@walkeros/runner` package, which the `walkeros/flow` image now runs. The CLI
20
+ no longer depends on `express`, `cors` or `p-limit`. New `@walkeros/core/node`
21
+ entry with the Node-only logger, redaction and temp-path helpers.
22
+ - 74821ed: `walkeros push --simulate` prints each step's mapping and vendor
23
+ calls (`simulations` in `--json`) and reports init or push failures. New
24
+ flags: `--ingest`, `--consent` (MCP `state.consent`), `--command` for command
25
+ examples, `--simulate collector.default` and `--mock collector.next.<id>`. A
26
+ destination that sent nothing says why in `skipped`. `toPrintable` is
27
+ exported.
28
+ - 74821ed: Simulate records every vendor call through one recorder, `observeEnv`
29
+ from `@walkeros/core`, and runs offline: BigQuery, Data Manager and the
30
+ Sheets, GCS and S3 stores reach the network through `env`. Client and `Env`
31
+ types of BigQuery, Firehose, PostHog, SQS and Pub/Sub are structural.
32
+ `@walkeros/cli` exports `resolveExportName` and `selectDevExamples` and drops
33
+ `findExample` and `compareOutput`.
34
+ - 74821ed: Simulate starts only the simulated step, and a simulated transformer
35
+ continues through its `next`. Source simulations list the commands a source
36
+ issues as `elb` calls; `--page-url` sets the web page. Express flows need no
37
+ port. Packages with several exports use per-export examples and mocks, and a
38
+ destination without a mock env is refused instead of calling the vendor.
39
+ - 74821ed: `walkeros validate` reports a missing or non-JSON input file as an
40
+ input error (exit 3). `--path` no longer fails on `uri` or email formats, nor
41
+ warns on mapping loops. The published Flow JSON Schema adds `config.observe`
42
+ and drops step-level `validate`. The Usercentrics schema now lists
43
+ `apiVersion` and `v3EventName`.
44
+ - 74821ed: `walkeros validate` prints a `Scope:` line and returns
45
+ `details.scope` (flows and checks) instead of `details.validatedFlow`;
46
+ `details.skipped` lists checks that did not run, such as an unreachable
47
+ package schema (exit 0). `--path` and `--flow` narrow every check; paths start
48
+ with `flows.<flow>.`. Errors and warnings carry stable codes, settings errors
49
+ `ENTRY_SCHEMA` plus `keyword`. `--path` or `--flow` with a non-flow `-t`
50
+ exits 3.
51
+ - 74821ed: `walkeros validate` warns on malformed or mid-string `$flow.`,
52
+ `$store.`, `$secret.` and `$contract.` references, paths that can never
53
+ resolve, unknown route targets, and routes shadowed by a `stop` or first
54
+ match. Contracts bind only on `@walkeros/transformer-validate` steps.
55
+ Cross-step checks include an object `out`.
21
56
 
22
57
  ### Patch Changes
23
58
 
24
- - ef02916: `walkeros validate --path` no longer fails with
25
- `unknown format "uri" ignored` for packages whose settings use URL or email
26
- fields. Settings are still checked for structure, types and patterns; string
27
- formats such as `uri` are not checked.
28
- - 8f8aea6: Every step field now survives bundling. A transformer with only
29
- `state` or `mapping`, and inline code steps with `cache` or `state`, were
30
- silently dropped from the bundle before and did nothing at runtime. `mapping`
31
- is now a typed transformer field, and bundles no longer carry `variables`.
32
- - Updated dependencies [57788bc]
33
- - Updated dependencies [2aebc53]
34
- - Updated dependencies [f5a1cfd]
35
- - Updated dependencies [ef02916]
36
- - Updated dependencies [ef02916]
37
- - Updated dependencies [2aebc53]
38
- - Updated dependencies [f5a1cfd]
39
- - Updated dependencies [f5a1cfd]
40
- - Updated dependencies [2aebc53]
41
- - Updated dependencies [8f8aea6]
42
- - Updated dependencies [2aebc53]
43
- - Updated dependencies [2aebc53]
44
- - @walkeros/core@4.7.0-next-1790187973605
45
- - @walkeros/server-core@4.7.0-next-1790187973605
46
- - @walkeros/collector@4.7.0-next-1790187973605
47
- - @walkeros/transformer-validate@4.7.0-next-1790187973605
48
- - @walkeros/server-destination-api@4.7.0-next-1790187973605
59
+ - 74821ed: Server builds served from the build cache now copy the root `include`
60
+ folders; web builds ignore `include` and log it. An unused package in
61
+ `bundle.packages` warns instead of failing the build. Cache entries are
62
+ written atomically, so an interrupt no longer leaves a broken entry, and
63
+ `walkeros cache clear` removes leftovers. Temp dirs are
64
+ `<tmp>/walkeros/<kind>/<id>`.
65
+ - 74821ed: A flow's own log lines now go through the CLI logger: its debug lines
66
+ need `--verbose`, and they go to stderr with `--json`. Version numbers are no
67
+ longer masked as tokens, so `walkeros deploy` shows the image tag and
68
+ `bundle --stats` shows package versions. Paths under the system temp directory
69
+ print as `$TMPDIR/...`.
70
+ - 74821ed: The values of secrets a flow references are masked in simulate
71
+ output, CLI logs and flow logs, also inside JSON strings. The runtime masks
72
+ the secret values it fetches in every log path, heartbeats and `--json` errors
73
+ included. Simulate output also scrubs credential-named fields, `Authorization`
74
+ headers and PEM keys. `scrubSecrets` takes `known`; the CLI logger takes
75
+ `knownSecrets`.
76
+ - 74821ed: `state` paths resolve against `{ event, ingest }` and need an
77
+ `event.` or `ingest.` prefix; a `get` can write into `ingest`, and an
78
+ unresolvable key warns. Every step field now survives bundling: transformers
79
+ with only `state` or `mapping`, and code steps with `cache` or `state`, were
80
+ silently dropped before. `buildCacheContext` is renamed `createMappingRoot`.
81
+ - Updated dependencies [74821ed]
82
+ - Updated dependencies [06b498a]
83
+ - Updated dependencies [74821ed]
84
+ - Updated dependencies [74821ed]
85
+ - Updated dependencies [74821ed]
86
+ - Updated dependencies [74821ed]
87
+ - Updated dependencies [06b498a]
88
+ - Updated dependencies [74821ed]
89
+ - Updated dependencies [74821ed]
90
+ - Updated dependencies [74821ed]
91
+ - Updated dependencies [74821ed]
92
+ - Updated dependencies [74821ed]
93
+ - Updated dependencies [74821ed]
94
+ - Updated dependencies [74821ed]
95
+ - @walkeros/collector@4.7.0-next-1790722899482
96
+ - @walkeros/core@4.7.0-next-1790722899482
97
+ - @walkeros/server-core@4.7.0-next-1790722899482
98
+ - @walkeros/transformer-validate@4.7.0-next-1790722899482
99
+ - @walkeros/server-destination-api@4.7.0-next-1790722899482
49
100
 
50
101
  ## 4.6.1
51
102
 
package/README.md CHANGED
@@ -22,14 +22,20 @@ npm install -g @walkeros/cli
22
22
  ## Quick start
23
23
 
24
24
  ```bash
25
- # Bundle a flow configuration
26
- walkeros bundle flow.json
27
-
28
25
  # Test with simulated events (no real API calls)
29
26
  walkeros push flow.json --event '{"name":"product view"}' --simulate destination.demo
30
27
 
31
- # Run a collection server locally
32
- walkeros run dist/flow.mjs --port 3000
28
+ # Bundle a flow configuration into dist/
29
+ walkeros bundle flow.json -o dist/
30
+ ```
31
+
32
+ The CLI builds flows; it does not run them. Start a built server flow with
33
+ `runneros` from
34
+ [`@walkeros/runner`](https://www.npmjs.com/package/@walkeros/runner) (also the
35
+ `walkeros/flow` Docker image):
36
+
37
+ ```bash
38
+ npx --package=@walkeros/runner runneros start dist/flow.mjs --port 3000
33
39
  ```
34
40
 
35
41
  ## Documentation