@walkeros/core 4.3.0-next-1781171238534 → 4.3.0-next-1783517345197
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 +47 -1
- package/dist/dev.d.mts +288 -8
- package/dist/dev.d.ts +288 -8
- package/dist/dev.js +1 -1
- package/dist/dev.js.map +1 -1
- package/dist/dev.mjs +1 -1
- package/dist/dev.mjs.map +1 -1
- package/dist/index.d.mts +530 -25
- package/dist/index.d.ts +530 -25
- package/dist/index.js +1 -1
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +1 -1
- package/dist/index.mjs.map +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,12 +1,58 @@
|
|
|
1
1
|
# @walkeros/core
|
|
2
2
|
|
|
3
|
-
## 4.3.0-next-
|
|
3
|
+
## 4.3.0-next-1783517345197
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- e01036e: Unknown walker commands now log a warning and return `ok: false`
|
|
8
|
+
instead of silently succeeding. The elb function is exposed as
|
|
9
|
+
`collector.elb`, a new required field on `Collector.Instance`, replacing the
|
|
10
|
+
internal `sources.elb` pseudo-source.
|
|
11
|
+
- e01036e: Flow observation records now carry per-event journey correlation: a
|
|
12
|
+
W3C `traceparent` links a web send to the server flow that receives it, plus
|
|
13
|
+
the originating source id and a monotonic sequence that makes dropped
|
|
14
|
+
telemetry visible. At trace level, destinations can opt in to recording their
|
|
15
|
+
outgoing vendor calls.
|
|
16
|
+
- 98801c9: Flow observation records now assemble into per-event journeys
|
|
17
|
+
spanning web and server flows, each hop showing input, output, and status,
|
|
18
|
+
with loss flagged; the `observe_journeys` MCP tool exposes the same journeys
|
|
19
|
+
to agents. Batching destinations now emit per-event records, and live-web
|
|
20
|
+
vendor calls are captured when a destination reaches its callable through
|
|
21
|
+
`getEnv`, though batched sends stay uncaptured.
|
|
22
|
+
- 9506e3e: Events now carry per-flow config provenance on
|
|
23
|
+
`event.source.release`, a flow-name to release map that accumulates as an
|
|
24
|
+
event crosses flows (web capture to server processing), so a delivered event
|
|
25
|
+
shows which config handled it. The collector no longer stamps `source.version`
|
|
26
|
+
(external source emitters may still set it). In this first version, aws and
|
|
27
|
+
gcp crossings are not yet covered.
|
|
28
|
+
|
|
29
|
+
## 4.2.1
|
|
4
30
|
|
|
5
31
|
### Patch Changes
|
|
6
32
|
|
|
7
33
|
- 5cbcd23: Simulation step results gain an optional `mappingKey` field reporting
|
|
8
34
|
the entity-action key of the mapping rule a destination matched during
|
|
9
35
|
simulation. The field is additive and present only when a rule matched.
|
|
36
|
+
- 31c6858: `getId` now draws from the platform's cryptographic random source
|
|
37
|
+
(`crypto.getRandomValues`) when available, with unbiased character sampling
|
|
38
|
+
and a `Math.random` fallback. Session and device ids generated by the session
|
|
39
|
+
source are now longer for a much wider collision margin.
|
|
40
|
+
- d1b41ca: The collector now stamps a run-scoped trace id (`event.source.trace`)
|
|
41
|
+
and a per-run sequence number (`event.source.count`) onto every event, minted
|
|
42
|
+
fresh on each `run`. These group all events of a page load or run and are
|
|
43
|
+
preserved unchanged when events are forwarded from web to server, giving a
|
|
44
|
+
stable correlation id across the pipeline. Adds `getTraceId`, and `getSpanId`
|
|
45
|
+
now uses the cryptographic random source.
|
|
46
|
+
- 0a8a08b: Add an optional `async` option to the source config
|
|
47
|
+
(`Source.Config.async`) for respond-first acknowledgement on
|
|
48
|
+
response-producing server sources. The express source now reads `config.async`
|
|
49
|
+
(default `true`): a 2xx response means the event was accepted, not yet
|
|
50
|
+
delivered.
|
|
51
|
+
- 8afb7cc: Add an optional `reportError` callback to the step context so any
|
|
52
|
+
source, transformer, store, or destination can report an out-of-band error
|
|
53
|
+
(for example from an SDK's event emitter) into the pipeline's failure
|
|
54
|
+
handling. Add an optional per-destination `breaker` config to skip a
|
|
55
|
+
destination after repeated transport failures.
|
|
10
56
|
|
|
11
57
|
## 4.2.0
|
|
12
58
|
|