github AgentWorkforce/burn relayburn-v2.8.6
relayburn@2.8.6

3 hours ago

Packages

  • relayburn@2.8.6 (tag: relayburn-v2.8.6)
  • @relayburn/sdk@2.8.6 (tag: sdk-v2.8.6)
  • @relayburn/mcp@2.8.6 (tag: mcp-v2.8.6)
  • @relayburn/cli-darwin-arm64@2.8.6 (tag: cli-darwin-arm64-v2.8.6)
  • @relayburn/cli-darwin-x64@2.8.6 (tag: cli-darwin-x64-v2.8.6)
  • @relayburn/cli-linux-arm64-gnu@2.8.6 (tag: cli-linux-arm64-gnu-v2.8.6)
  • @relayburn/cli-linux-x64-gnu@2.8.6 (tag: cli-linux-x64-gnu-v2.8.6)
  • @relayburn/sdk-darwin-arm64@2.8.6 (tag: sdk-darwin-arm64-v2.8.6)
  • @relayburn/sdk-darwin-x64@2.8.6 (tag: sdk-darwin-x64-v2.8.6)
  • @relayburn/sdk-linux-arm64-gnu@2.8.6 (tag: sdk-linux-arm64-gnu-v2.8.6)
  • @relayburn/sdk-linux-x64-gnu@2.8.6 (tag: sdk-linux-x64-gnu-v2.8.6)

Crates

Release Notes

Changed

  • relayburn-cli: burn compare --since now uses the same normalization path
    as burn summary and burn hotspots, keeping date-filter behavior
    consistent across commands.
  • relayburn-sdk: normalize_since now canonicalizes outputs to UTC
    YYYY-MM-DDTHH:MM:SS.mmmZ. Relative ranges (7d, 24h) emit .000Z
    instead of Z, and ISO inputs with offsets (e.g. ...-07:00) are
    converted to UTC. This fixes burn summary / burn hotspots /
    burn compare --since silently dropping same-second turns and misordering
    offset cutoffs against the ledger's ts >= ? lex compare.

Don't miss a new burn release

NewReleases is sending notifications on new releases.