@walkeros/cli 4.7.0-next-1790722899482 → 4.7.1-next-1791015692826

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,6 +1,33 @@
1
1
  # @walkeros/cli
2
2
 
3
- ## 4.7.0-next-1790722899482
3
+ ## 4.7.1-next-1791015692826
4
+
5
+ ### Patch Changes
6
+
7
+ - 91e9aeb: New `walkeros diagnostics` command shows the CLI version, app URL,
8
+ app health and an API compatibility verdict checked per operation against the
9
+ live app; the MCP `diagnostics` tool reports it too and
10
+ `walkeros://reference/openapi` serves the live document. `compareContract` and
11
+ `ContractComparison` are reshaped, `annotateErrorWithDrift` is removed, and
12
+ deployment listing rejects an unknown `status` or `type`.
13
+ - 0635330: Web bundles now leave out features the flow does not use. The minimal
14
+ web flow drops from about 115 KB to 93 KB (40 KB to 32 KB gzipped). Skeletons
15
+ built by older CLI versions still wrap with every feature.
16
+ - bd511d0: Web flows with the Mixpanel or PostHog destination can now be pushed
17
+ and simulated. Simulating a web flow no longer loads vendor scripts, and
18
+ simulating a source no longer starts the flow's destinations. A web push
19
+ records XMLHttpRequest calls like fetch and sendBeacon, listed as
20
+ `networkCalls` in `--json`.
21
+ - Updated dependencies [0635330]
22
+ - Updated dependencies [0635330]
23
+ - Updated dependencies [91e9aeb]
24
+ - @walkeros/collector@4.7.1-next-1791015692826
25
+ - @walkeros/core@4.7.1-next-1791015692826
26
+ - @walkeros/server-core@4.7.1-next-1791015692826
27
+ - @walkeros/server-destination-api@4.7.1-next-1791015692826
28
+ - @walkeros/transformer-validate@4.7.1-next-1791015692826
29
+
30
+ ## 4.7.0
4
31
 
5
32
  ### Minor Changes
6
33
 
@@ -9,6 +36,16 @@
9
36
  `config.bundle.env`; they must be literal strings and supply `$env` in web
10
37
  bundles. Step packages, overrides and their dependencies must now come from
11
38
  the npm registry: git, file and URL specs are rejected.
39
+ - 64b06de: A bundle's default release is now a content id of config, packages
40
+ and CLI version, so repeat builds hit the build cache. Env and secret values
41
+ are not part of it, only their names. `--release` now beats a flow's
42
+ `collector.release`. Rebuilt local `path` packages and CLI upgrades invalidate
43
+ the build caches, and `cache clear --builds` also clears compiled code.
44
+ - 64b06de: Packages with several exports, such as the GCP and AWS sources and
45
+ destinations, now publish a settings schema per export. `walkeros validate`
46
+ and MCP `package_get` use the schema of the export a step imports. Pub/Sub,
47
+ BigQuery, SNS and SQS steps pinned to this release or later are checked
48
+ instead of skipped; older pins still report a skip.
12
49
  - 74821ed: The canonical `flow-complete.json` example is rewritten as one tested
13
50
  ecommerce setup with web, server and warehouse flows and a 15-chapter guide.
14
51
  The new `flowCompleteManifest` export from `@walkeros/cli/examples` names
@@ -36,51 +73,91 @@
36
73
  issues as `elb` calls; `--page-url` sets the web page. Express flows need no
37
74
  port. Packages with several exports use per-export examples and mocks, and a
38
75
  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`.
76
+ - 4b4937f: Files that passed `walkeros validate` may now fail: it checks every
77
+ flow and every step's package settings unless you narrow it, and resolves each
78
+ flow as the bundler does, so an unresolvable `$flow` is an error. `--path`
79
+ checks the entry in every flow. Settings findings warn for one minor.
80
+ Named-export steps are skipped; `--offline` skips fetching.
81
+ - 74821ed: `walkeros validate` reports a missing or non-JSON input as exit 3,
82
+ like `--path`, `--flow` or `--offline` with a non-flow `-t`. Unknown keys on
83
+ destinations and stores warn (`UNKNOWN_KEY`), as does
84
+ `@walkeros/store-memory`. `--path` ignores `uri` and email formats. The Flow
85
+ JSON Schema adds `config.observe` and drops step-level `validate`; the
86
+ Usercentrics schema lists `apiVersion` and `v3EventName`.
44
87
  - 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`.
88
+ `details.scope` instead of `details.validatedFlow`, `details.skipped` for
89
+ checks that did not run and `details.deferred` for values known only at
90
+ runtime. Skips never read as passed. Every finding has a stable `code`.
91
+ `--strict` fails on warnings or skips (exit 2), and `validate()` and
92
+ `flow_validate` with `strict` return `valid: false`; `flow_validate` also
93
+ accepts `offline`.
94
+ - 74821ed: An unknown `$var` or `$store` now fails `walkeros validate`, as it
95
+ fails the bundle. References resolve per flow, and `description` text is never
96
+ read as a reference. A dangling contract `extend`, an unknown `$contract` on a
97
+ validate step, or a contract cycle is an error. Contracts bind only on
98
+ validate steps. Malformed references and unknown or shadowed routes warn.
99
+ - 4f89234: Web builds now assign the collector to the global named in
100
+ `config.settings.windowCollector`, default `walkerOS`. Before,
101
+ `walkeros bundle` ignored the setting. It accepts a name or a `$var`/`$env`
102
+ reference; the resolved name must be a valid, non-reserved JavaScript
103
+ identifier, or the build and `walkeros validate` report an error.
56
104
 
57
105
  ### Patch Changes
58
106
 
107
+ - 786a860: AWS destinations now deliver in bundled flows without extra setup.
108
+ Firehose batches by default, ends records with a newline (`newline: false`
109
+ turns it off), sends mapped `data` and accepts `config.credentials`. Rejected
110
+ records now count as failed. SNS works with `topicArn` alone and no longer
111
+ creates topics at start. `walkeros setup` resolves `$secret` values; partial
112
+ batch failures log their causes.
59
113
  - 74821ed: Server builds served from the build cache now copy the root `include`
60
114
  folders; web builds ignore `include` and log it. An unused package in
61
115
  `bundle.packages` warns instead of failing the build. Cache entries are
62
116
  written atomically, so an interrupt no longer leaves a broken entry, and
63
117
  `walkeros cache clear` removes leftovers. Temp dirs are
64
118
  `<tmp>/walkeros/<kind>/<id>`.
119
+ - 5a210e1: `walkeros flows create` and `walkeros flows update` now read
120
+ `--content` from a file path or URL as well as an inline JSON string. Large
121
+ flows no longer need to fit on the command line: pass `--content ./flow.json`.
65
122
  - 74821ed: A flow's own log lines now go through the CLI logger: its debug lines
66
123
  need `--verbose`, and they go to stderr with `--json`. Version numbers are no
67
124
  longer masked as tokens, so `walkeros deploy` shows the image tag and
68
125
  `bundle --stats` shows package versions. Paths under the system temp directory
69
126
  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`.
127
+ - b1e5aa5: Manifest builds now survive short network blips: the manifest
128
+ download, skeleton downloads and uploads retry up to three times on network
129
+ errors, timeouts, 5xx and 429, while other statuses such as an expired link
130
+ fail at once. Each retry is logged, and errors name the cause, for example
131
+ `fetch failed (ECONNRESET)` or `HTTP 503`.
132
+ - 74821ed: Simulate and push output, CLI and flow logs, and the MCP
133
+ `flow_simulate` and `flow_push` results mask the values of secrets a flow
134
+ references, also inside JSON strings, numbers and URLs. `scrubSecrets` takes
135
+ `known`, the CLI logger `knownSecrets`, and `scrubJson` replaces
136
+ `maskKnownNumbers`. MCP `flow_push` and `flow_simulate` read their config
137
+ once; a config that cannot be read stops the run.
138
+ - 050d776: Simulated click and impression examples of the browser source carry
139
+ `source` and `globals` again. A page scope from another realm, such as an
140
+ iframe or a simulated page, is now recognized. Simulate also exposes `Node`,
141
+ `Element`, `HTMLElement`, `Document` and `ShadowRoot`, so `instanceof` checks
142
+ behave as in a browser.
76
143
  - 74821ed: `state` paths resolve against `{ event, ingest }` and need an
77
144
  `event.` or `ingest.` prefix; a `get` can write into `ingest`, and an
78
145
  unresolvable key warns. Every step field now survives bundling: transformers
79
146
  with only `state` or `mapping`, and code steps with `cache` or `state`, were
80
147
  silently dropped before. `buildCacheContext` is renamed `createMappingRoot`.
148
+ - e860006: `state` gains `mapping` to shape what a lookup returns or a write
149
+ stores, merged into the target. An undeclared `state.store`, or a `file: true`
150
+ store, is now a validation error in `walkeros validate` and deploy preflight;
151
+ at runtime the entry logs an error or is skipped with a warning. The s3 and
152
+ gcs stores report their `file` mode.
153
+ - Updated dependencies [786a860]
81
154
  - Updated dependencies [74821ed]
82
155
  - Updated dependencies [06b498a]
156
+ - Updated dependencies [7e5e3de]
157
+ - Updated dependencies [b9668bf]
83
158
  - Updated dependencies [74821ed]
159
+ - Updated dependencies [64b06de]
160
+ - Updated dependencies [4b4937f]
84
161
  - Updated dependencies [74821ed]
85
162
  - Updated dependencies [74821ed]
86
163
  - Updated dependencies [74821ed]
@@ -90,13 +167,15 @@
90
167
  - Updated dependencies [74821ed]
91
168
  - Updated dependencies [74821ed]
92
169
  - Updated dependencies [74821ed]
170
+ - Updated dependencies [e860006]
93
171
  - Updated dependencies [74821ed]
94
172
  - 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
173
+ - Updated dependencies [4f89234]
174
+ - @walkeros/collector@4.7.0
175
+ - @walkeros/core@4.7.0
176
+ - @walkeros/server-core@4.7.0
177
+ - @walkeros/transformer-validate@4.7.0
178
+ - @walkeros/server-destination-api@4.7.0
100
179
 
101
180
  ## 4.6.1
102
181