@walkeros/core 4.6.1 → 4.7.0-next-1790245733116

package/CHANGELOG.md

@@ -1,5 +1,72 @@
 # @walkeros/core
 
+## 4.7.0-next-1790245733116
+
+### Minor Changes
+
+- 57788bc: `anonymizeIP` now handles IPv6, keeping the first 48 bits, and treats
+  an IPv4-mapped address (`::ffff:1.2.3.4`) as IPv4; both returned an empty
+  string before. `getHashServer` takes an optional `key` for a keyed HMAC hash;
+  without it the output is unchanged.
+- 06b498a: `walkeros bundle --manifest <url|path>` builds every artifact a build
+  manifest lists and uploads each one with a result. Declare build values in
+  `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.
+- f5a1cfd: New `collector.next`: a transformer chain that runs once per event,
+  before the event is handed to the destinations. Everything it produces reaches
+  every destination, and a `stop` in it drops the event for all of them;
+  per-destination filtering stays on `destination.before`. The explorer flow map
+  draws this chain, and the MCP guidance describes it.
+- 06b498a: New `@walkeros/core/node` entry point with the Node-only helpers the
+  CLI and the runner both share: `scrubSecrets`, `redactLine`,
+  `createCLILogger`, `createCLILoggerConfig`, `getTmpPath`, `createTmpResolver`
+  and `getDefaultTmpRoot`. The main entry gains `createTimer` and
+  `getErrorMessage`.
+- 2aebc53: A mapping value now runs exactly one producer, in the order `loop`,
+  `map`, `set`, `key`, `fn`; the rest never run, so a `fn` next to a `key` is
+  ignored. To transform a field, use `fn` alone. A `loop` over something that is
+  not a list now yields the `value` fallback instead of the whole event.
+- f5a1cfd: Inside an array, a transformer's own `next` now runs right after it,
+  then the array continues. `many` works in every chain field: each match
+  becomes its own copy with a derived `event.id` that finishes the rest of the
+  path. Unknown transformer ids log a warning and the chain continues.
+  `@walkeros/collector` no longer exports `walkChain` or
+  `extractTransformerNextMap`.
+- f5a1cfd: Routes can drop an event with `{ stop: true }`, optionally gated by
+  `match`, in every chain field. A route `match` now reads `{ ingest, event }`
+  and resolves only when the event reaches it, so it sees values earlier steps
+  loaded. `getNextSteps(spec, root)` now requires that root and returns
+  `NextSteps`; the new `getRouteGraph` lists every branch.
+- 2aebc53: `state` paths now resolve against `{ event, ingest }` and need an
+  `event.` or `ingest.` prefix, so a store can be keyed by request context. A
+  `get` can write into `ingest`, keeping the value off the event. An
+  unresolvable key logs a warning instead of failing silently.
+  `buildCacheContext` is renamed `createMappingRoot`.
+- 8f8aea6: Every step field now survives bundling. A transformer with only
+  `state` or `mapping`, and inline code steps with `cache` or `state`, were
+  silently dropped from the bundle before and did nothing at runtime. `mapping`
+  is now a typed transformer field, and bundles no longer carry `variables`.
+- 2aebc53: `walkeros validate` now reports paths that can never resolve: an
+  `ingest.` path in mapping `data` or `policy`, which resolve against the event,
+  and a cache key or route match without an `event.` or `ingest.` prefix. Flow
+  steps now declare `state`, so its paths are validated too.
+- 2aebc53: A mapping or `policy` entry that resolves to nothing now removes the
+  field instead of leaving an `undefined` placeholder, so a denied consent gate
+  redacts it. The validate transformer never throws: an engine failure becomes
+  an issue, and `pass` mode no longer drops events that carry such fields.
+
+### Patch Changes
+
+- ef02916: The JSON Schema for a mapping loop now sets `minItems` and `maxItems`
+  to 2, so a settings schema that embeds a mapping value no longer makes
+  `walkeros validate --path` print an Ajv strict-mode warning. The published
+  Flow JSON Schema (`schema/flow/v4.json`) was refreshed to match: it now
+  includes `config.observe` and no longer lists the step-level `validate` field.
+- ef02916: The destination `queue` option's description now says what it does:
+  whether a destination added later receives the run's earlier events (default
+  true). Consent-denied events are queued regardless.
+
 ## 4.6.1
 
 ## 4.6.0