github AgentWorkforce/burn relayburn-v4.0.0
relayburn@4.0.0

4 hours ago

Packages

  • relayburn@4.0.0 (tag: relayburn-v4.0.0)
  • @relayburn/sdk@4.0.0 (tag: sdk-v4.0.0)
  • @relayburn/mcp@4.0.0 (tag: mcp-v4.0.0)
  • @relayburn/cli-darwin-arm64@4.0.0 (tag: cli-darwin-arm64-v4.0.0)
  • @relayburn/cli-darwin-x64@4.0.0 (tag: cli-darwin-x64-v4.0.0)
  • @relayburn/cli-linux-arm64-gnu@4.0.0 (tag: cli-linux-arm64-gnu-v4.0.0)
  • @relayburn/cli-linux-x64-gnu@4.0.0 (tag: cli-linux-x64-gnu-v4.0.0)
  • @relayburn/sdk-darwin-arm64@4.0.0 (tag: sdk-darwin-arm64-v4.0.0)
  • @relayburn/sdk-darwin-x64@4.0.0 (tag: sdk-darwin-x64-v4.0.0)
  • @relayburn/sdk-linux-arm64-gnu@4.0.0 (tag: sdk-linux-arm64-gnu-v4.0.0)
  • @relayburn/sdk-linux-x64-gnu@4.0.0 (tag: sdk-linux-x64-gnu-v4.0.0)

Crates

Release Notes

  • BREAKING (relayburn-sdk): the published Rust SDK no longer re-exports its low-level analyze-layer internals (detector/aggregator functions and helper types such as PricingTable, CompareTable, CompareCell) — these were never the intended embedding surface. Embed through the verb layer instead: LedgerHandle methods / summary_report / hotspots / compare. CLI, MCP, and @relayburn/sdk behavior is unchanged.
  • burn compare cost figures now use canonical decimal rounding ({:.N}/toFixed semantics) instead of float-multiply rounding, so cells/totals/buckets can shift by one in the last reported digit at exact ties; affects the compare verb's JSON for all consumers (CLI, MCP, @relayburn/sdk).
  • Fidelity summaries (fidelity block in summary/compare JSON) now emit byClass / byGranularity / missingCoverage keys in a stable order instead of a randomized per-run order, so output is reproducible across runs (diff-, cache-, and snapshot-friendly).
  • burn subagent-tree views now require a re-ingest to render pre-Root-emission event logs (legacy reconstruction path removed).

Package Changelogs

relayburn

  • burn compare cost figures now use canonical decimal rounding ({:.N}/toFixed semantics), so cells/totals/buckets can shift by one in the last reported digit at exact ties.
  • fidelity blocks in summary / compare JSON now emit byClass / byGranularity / missingCoverage keys in a stable order, so output is reproducible across runs.

@relayburn/sdk

  • compare() cost figures now use canonical decimal rounding (toFixed semantics) instead of float-multiply rounding, so cells/totals can shift by one in the last reported digit at exact ties.
  • Fidelity summaries (byClass / byGranularity / missingCoverage) now have a stable key order instead of a randomized per-call order, so results are reproducible.

@relayburn/mcp

  • compare / summary tool output reflects the SDK's canonical compare-cost rounding (toFixed semantics; ties shift by one in the last digit) and a stable, deterministic fidelity-summary key order.

Don't miss a new burn release

NewReleases is sending notifications on new releases.