@walkeros/cli 4.7.0-next-1790722899482 → 4.7.0

package/CHANGELOG.md

@@ -1,6 +1,6 @@
 # @walkeros/cli
 
-## 4.7.0-next-1790722899482
+## 4.7.0
 
 ### Minor Changes
 
@@ -9,6 +9,16 @@
   `config.bundle.env`; they must be literal strings and supply `$env` in web
   bundles. Step packages, overrides and their dependencies must now come from
   the npm registry: git, file and URL specs are rejected.
+- 64b06de: A bundle's default release is now a content id of config, packages
+  and CLI version, so repeat builds hit the build cache. Env and secret values
+  are not part of it, only their names. `--release` now beats a flow's
+  `collector.release`. Rebuilt local `path` packages and CLI upgrades invalidate
+  the build caches, and `cache clear --builds` also clears compiled code.
+- 64b06de: Packages with several exports, such as the GCP and AWS sources and
+  destinations, now publish a settings schema per export. `walkeros validate`
+  and MCP `package_get` use the schema of the export a step imports. Pub/Sub,
+  BigQuery, SNS and SQS steps pinned to this release or later are checked
+  instead of skipped; older pins still report a skip.
 - 74821ed: The canonical `flow-complete.json` example is rewritten as one tested
   ecommerce setup with web, server and warehouse flows and a 15-chapter guide.
   The new `flowCompleteManifest` export from `@walkeros/cli/examples` names
@@ -36,51 +46,91 @@
   issues as `elb` calls; `--page-url` sets the web page. Express flows need no
   port. Packages with several exports use per-export examples and mocks, and a
   destination without a mock env is refused instead of calling the vendor.
-- 74821ed: `walkeros validate` reports a missing or non-JSON input file as an
-  input error (exit 3). `--path` no longer fails on `uri` or email formats, nor
-  warns on mapping loops. The published Flow JSON Schema adds `config.observe`
-  and drops step-level `validate`. The Usercentrics schema now lists
-  `apiVersion` and `v3EventName`.
+- 4b4937f: Files that passed `walkeros validate` may now fail: it checks every
+  flow and every step's package settings unless you narrow it, and resolves each
+  flow as the bundler does, so an unresolvable `$flow` is an error. `--path`
+  checks the entry in every flow. Settings findings warn for one minor.
+  Named-export steps are skipped; `--offline` skips fetching.
+- 74821ed: `walkeros validate` reports a missing or non-JSON input as exit 3,
+  like `--path`, `--flow` or `--offline` with a non-flow `-t`. Unknown keys on
+  destinations and stores warn (`UNKNOWN_KEY`), as does
+  `@walkeros/store-memory`. `--path` ignores `uri` and email formats. The Flow
+  JSON Schema adds `config.observe` and drops step-level `validate`; the
+  Usercentrics schema lists `apiVersion` and `v3EventName`.
 - 74821ed: `walkeros validate` prints a `Scope:` line and returns
-  `details.scope` (flows and checks) instead of `details.validatedFlow`;
-  `details.skipped` lists checks that did not run, such as an unreachable
-  package schema (exit 0). `--path` and `--flow` narrow every check; paths start
-  with `flows.<flow>.`. Errors and warnings carry stable codes, settings errors
-  `ENTRY_SCHEMA` plus `keyword`. `--path` or `--flow` with a non-flow `-t`
-  exits 3.
-- 74821ed: `walkeros validate` warns on malformed or mid-string `$flow.`,
-  `$store.`, `$secret.` and `$contract.` references, paths that can never
-  resolve, unknown route targets, and routes shadowed by a `stop` or first
-  match. Contracts bind only on `@walkeros/transformer-validate` steps.
-  Cross-step checks include an object `out`.
+  `details.scope` instead of `details.validatedFlow`, `details.skipped` for
+  checks that did not run and `details.deferred` for values known only at
+  runtime. Skips never read as passed. Every finding has a stable `code`.
+  `--strict` fails on warnings or skips (exit 2), and `validate()` and
+  `flow_validate` with `strict` return `valid: false`; `flow_validate` also
+  accepts `offline`.
+- 74821ed: An unknown `$var` or `$store` now fails `walkeros validate`, as it
+  fails the bundle. References resolve per flow, and `description` text is never
+  read as a reference. A dangling contract `extend`, an unknown `$contract` on a
+  validate step, or a contract cycle is an error. Contracts bind only on
+  validate steps. Malformed references and unknown or shadowed routes warn.
+- 4f89234: Web builds now assign the collector to the global named in
+  `config.settings.windowCollector`, default `walkerOS`. Before,
+  `walkeros bundle` ignored the setting. It accepts a name or a `$var`/`$env`
+  reference; the resolved name must be a valid, non-reserved JavaScript
+  identifier, or the build and `walkeros validate` report an error.
 
 ### Patch Changes
 
+- 786a860: AWS destinations now deliver in bundled flows without extra setup.
+  Firehose batches by default, ends records with a newline (`newline: false`
+  turns it off), sends mapped `data` and accepts `config.credentials`. Rejected
+  records now count as failed. SNS works with `topicArn` alone and no longer
+  creates topics at start. `walkeros setup` resolves `$secret` values; partial
+  batch failures log their causes.
 - 74821ed: Server builds served from the build cache now copy the root `include`
   folders; web builds ignore `include` and log it. An unused package in
   `bundle.packages` warns instead of failing the build. Cache entries are
   written atomically, so an interrupt no longer leaves a broken entry, and
   `walkeros cache clear` removes leftovers. Temp dirs are
   `<tmp>/walkeros/<kind>/<id>`.
+- 5a210e1: `walkeros flows create` and `walkeros flows update` now read
+  `--content` from a file path or URL as well as an inline JSON string. Large
+  flows no longer need to fit on the command line: pass `--content ./flow.json`.
 - 74821ed: A flow's own log lines now go through the CLI logger: its debug lines
   need `--verbose`, and they go to stderr with `--json`. Version numbers are no
   longer masked as tokens, so `walkeros deploy` shows the image tag and
   `bundle --stats` shows package versions. Paths under the system temp directory
   print as `$TMPDIR/...`.
-- 74821ed: The values of secrets a flow references are masked in simulate
-  output, CLI logs and flow logs, also inside JSON strings. The runtime masks
-  the secret values it fetches in every log path, heartbeats and `--json` errors
-  included. Simulate output also scrubs credential-named fields, `Authorization`
-  headers and PEM keys. `scrubSecrets` takes `known`; the CLI logger takes
-  `knownSecrets`.
+- b1e5aa5: Manifest builds now survive short network blips: the manifest
+  download, skeleton downloads and uploads retry up to three times on network
+  errors, timeouts, 5xx and 429, while other statuses such as an expired link
+  fail at once. Each retry is logged, and errors name the cause, for example
+  `fetch failed (ECONNRESET)` or `HTTP 503`.
+- 74821ed: Simulate and push output, CLI and flow logs, and the MCP
+  `flow_simulate` and `flow_push` results mask the values of secrets a flow
+  references, also inside JSON strings, numbers and URLs. `scrubSecrets` takes
+  `known`, the CLI logger `knownSecrets`, and `scrubJson` replaces
+  `maskKnownNumbers`. MCP `flow_push` and `flow_simulate` read their config
+  once; a config that cannot be read stops the run.
+- 050d776: Simulated click and impression examples of the browser source carry
+  `source` and `globals` again. A page scope from another realm, such as an
+  iframe or a simulated page, is now recognized. Simulate also exposes `Node`,
+  `Element`, `HTMLElement`, `Document` and `ShadowRoot`, so `instanceof` checks
+  behave as in a browser.
 - 74821ed: `state` paths resolve against `{ event, ingest }` and need an
   `event.` or `ingest.` prefix; a `get` can write into `ingest`, and an
   unresolvable key warns. Every step field now survives bundling: transformers
   with only `state` or `mapping`, and code steps with `cache` or `state`, were
   silently dropped before. `buildCacheContext` is renamed `createMappingRoot`.
+- e860006: `state` gains `mapping` to shape what a lookup returns or a write
+  stores, merged into the target. An undeclared `state.store`, or a `file: true`
+  store, is now a validation error in `walkeros validate` and deploy preflight;
+  at runtime the entry logs an error or is skipped with a warning. The s3 and
+  gcs stores report their `file` mode.
+- Updated dependencies [786a860]
 - Updated dependencies [74821ed]
 - Updated dependencies [06b498a]
+- Updated dependencies [7e5e3de]
+- Updated dependencies [b9668bf]
 - Updated dependencies [74821ed]
+- Updated dependencies [64b06de]
+- Updated dependencies [4b4937f]
 - Updated dependencies [74821ed]
 - Updated dependencies [74821ed]
 - Updated dependencies [74821ed]
@@ -90,13 +140,15 @@
 - Updated dependencies [74821ed]
 - Updated dependencies [74821ed]
 - Updated dependencies [74821ed]
+- Updated dependencies [e860006]
 - Updated dependencies [74821ed]
 - Updated dependencies [74821ed]
-  - @walkeros/collector@4.7.0-next-1790722899482
-  - @walkeros/core@4.7.0-next-1790722899482
-  - @walkeros/server-core@4.7.0-next-1790722899482
-  - @walkeros/transformer-validate@4.7.0-next-1790722899482
-  - @walkeros/server-destination-api@4.7.0-next-1790722899482
+- Updated dependencies [4f89234]
+  - @walkeros/collector@4.7.0
+  - @walkeros/core@4.7.0
+  - @walkeros/server-core@4.7.0
+  - @walkeros/transformer-validate@4.7.0
+  - @walkeros/server-destination-api@4.7.0
 
 ## 4.6.1