@walkeros/cli 4.3.0-next-1781171238534 → 4.3.0-next-1783517345197

package/CHANGELOG.md

@@ -1,14 +1,47 @@
 # @walkeros/cli
 
-## 4.3.0-next-1781171238534
+## 4.3.0-next-1783517345197
 
 ### Minor Changes
 
-- 5cbcd23: `walkeros run` reads two new environment variables.
-  `WALKEROS_OBSERVE_LEVEL` sets the runtime's baseline telemetry level (`off`,
-  `standard`, or `trace`). `WALKEROS_CONFIG_FROZEN` (`1` or `true`) serves the
-  bundle as an immutable snapshot: secrets are still injected at boot, but
-  config hot-swap and heartbeat are disabled.
+- e01036e: Web bundles no longer assign `window.elb`; the browser source owns
+  that global. The `windowElb` setting is deprecated: its value is forwarded to
+  the browser source's `config.settings.elb` with a warning, so custom global
+  names keep working.
+- e01036e: Flow observation records now carry per-event journey correlation: a
+  W3C `traceparent` links a web send to the server flow that receives it, plus
+  the originating source id and a monotonic sequence that makes dropped
+  telemetry visible. At trace level, destinations can opt in to recording their
+  outgoing vendor calls.
+- 98801c9: Flow observation records now assemble into per-event journeys
+  spanning web and server flows, each hop showing input, output, and status,
+  with loss flagged; the `observe_journeys` MCP tool exposes the same journeys
+  to agents. Batching destinations now emit per-event records, and live-web
+  vendor calls are captured when a destination reaches its callable through
+  `getEnv`, though batched sends stay uncaptured.
+- 9506e3e: Events now carry per-flow config provenance on
+  `event.source.release`, a flow-name to release map that accumulates as an
+  event crosses flows (web capture to server processing), so a delivered event
+  shows which config handled it. The collector no longer stamps `source.version`
+  (external source emitters may still set it). In this first version, aws and
+  gcp crossings are not yet covered.
+
+### Patch Changes
+
+- 06c93b4: Update the runtime Docker base image to Node.js 22.23.0, which
+  patches the Node.js June 2026 security release. The `walkeros/flow` and
+  `walkeros/cli` images now pin a fixed, digest-locked Node version.
+- Updated dependencies [e01036e]
+- Updated dependencies [e01036e]
+- Updated dependencies [98801c9]
+- Updated dependencies [9506e3e]
+  - @walkeros/collector@4.3.0-next-1783517345197
+  - @walkeros/core@4.3.0-next-1783517345197
+  - @walkeros/server-core@4.3.0-next-1783517345197
+  - @walkeros/server-destination-api@4.3.0-next-1783517345197
+  - @walkeros/transformer-validate@4.3.0-next-1783517345197
+
+## 4.2.1
 
 ### Patch Changes
 
@@ -19,18 +52,44 @@
   Failures print a stable, machine-readable error code (with a `Retry-After`
   hint on rate limits), and `deploy create` no longer prints an empty token
   placeholder.
+- ec84331: The managed flow runner now retries its bundle, config, and secret
+  fetches on transient failures (timeouts, network errors, 5xx) with bounded,
+  jittered backoff capped well inside the container health window, and the
+  secret fetch is now bounded by a timeout. A brief outage while a flow
+  container starts no longer hard-fails the run.
+- 4809699: The managed flow runner now reports its recent errors and recent log
+  output in its heartbeat, so deployed flows can surface runtime errors and logs
+  in the app without any external log tooling. Secrets are redacted before
+  leaving the runner.
+- 5cbcd23: `walkeros run` reads two new environment variables.
+  `WALKEROS_OBSERVE_LEVEL` sets the runtime's baseline telemetry level (`off`,
+  `standard`, or `trace`). `WALKEROS_CONFIG_FROZEN` (`1` or `true`) serves the
+  bundle as an immutable snapshot: secrets are still injected at boot, but
+  config hot-swap and heartbeat are disabled.
 - 5cbcd23: All four simulate functions (`simulateSource`, `simulateTransformer`,
   `simulateCollector`, `simulateDestination`) accept a new `data` option to run
   an existing bundle with updated configuration values, without rebundling. The
   new `buildDataPayload`, `classifyStepProperties`, and `containsCodeMarkers`
   exports build and inspect that payload. Destination simulation results now
   include `mappingKey`, the entity-action key of the matched mapping rule.
+- 8afb7cc: The runner registers its process-error guards before startup and
+  degrades its readiness check after repeated out-of-band errors, so a wedged
+  container is recycled instead of silently hot-looping. Heartbeats now flush
+  immediately on a new error and on shutdown, persist errors to disk so a
+  failure cause survives a restart, and report their configured interval.
+- Updated dependencies [bd9188d]
+- Updated dependencies [d8aebd1]
 - Updated dependencies [5cbcd23]
-  - @walkeros/core@4.3.0-next-1781171238534
-  - @walkeros/collector@4.3.0-next-1781171238534
-  - @walkeros/server-core@4.3.0-next-1781171238534
-  - @walkeros/server-destination-api@4.3.0-next-1781171238534
-  - @walkeros/transformer-validate@4.3.0-next-1781171238534
+- Updated dependencies [31c6858]
+- Updated dependencies [d1b41ca]
+- Updated dependencies [0a8a08b]
+- Updated dependencies [8afb7cc]
+- Updated dependencies [8afb7cc]
+  - @walkeros/collector@4.2.1
+  - @walkeros/core@4.2.1
+  - @walkeros/server-core@4.2.1
+  - @walkeros/server-destination-api@4.2.1
+  - @walkeros/transformer-validate@4.2.1
 
 ## 4.2.0