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

package/CHANGELOG.md

@@ -1,6 +1,16 @@
 # @walkeros/core
 
-## 4.7.0-next-1790722899482
+## 4.7.1-next-1791015692826
+
+### Patch Changes
+
+- 0635330: Adds build-time flags that let a bundler leave unused features out of
+  a browser bundle. Nothing changes when they are not set.
+- 91e9aeb: A `consent` key on a `loop` item neither unlocks nor holds back a
+  value inside that loop; the event's consent decides. This applies to
+  destination, source and state mappings alike.
+
+## 4.7.0
 
 ### Minor Changes
 
@@ -19,6 +29,16 @@
   chain field can drop an event with `{ stop: true }`, optionally gated by
   `match`. A route `match` reads `{ ingest, event }` when the event reaches it.
   New `getRouteGraph`; `getNextSteps(spec, root)` requires its root.
+- 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.
+- 4b4937f: `getFlowSettings` throws a typed `FlowCycleError` for `$flow` and
+  `$var` cycles, with `code` (`FLOW_CYCLE` or `VAR_CYCLE`) and the `chain` of
+  names; the message is unchanged. `validateFlowConfig` reference warnings now
+  carry the path of the value that holds the reference, and an unresolvable root
+  `contract` is an error at `contract`.
 - 74821ed: `anonymizeIP` now handles IPv6 (first 48 bits) and IPv4-mapped
   addresses; `getHashServer` takes an optional HMAC `key`. The fingerprint
   transformer works with just `{ salt }`: it hashes the anonymized IP, reduced
@@ -39,12 +59,12 @@
   `@walkeros/runner` package, which the `walkeros/flow` image now runs. The CLI
   no longer depends on `express`, `cors` or `p-limit`. New `@walkeros/core/node`
   entry with the Node-only logger, redaction and temp-path helpers.
-- 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`.
+- 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.
 - 74821ed: `walkeros push --simulate` prints each step's mapping and vendor
   calls (`simulations` in `--json`) and reports init or push failures. New
   flags: `--ingest`, `--consent` (MCP `state.consent`), `--command` for command
@@ -62,11 +82,21 @@
   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`.
-- 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`.
+- 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.
+- 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
 
@@ -75,11 +105,12 @@
   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`.
+- 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`.
 
 ## 4.6.1