github AgentWorkforce/burn relayburn-v3.1.0
relayburn@3.1.0

5 hours ago

Packages

  • relayburn@3.1.0 (tag: relayburn-v3.1.0)
  • @relayburn/sdk@3.1.0 (tag: sdk-v3.1.0)
  • @relayburn/mcp@3.1.0 (tag: mcp-v3.1.0)
  • @relayburn/cli-darwin-arm64@3.1.0 (tag: cli-darwin-arm64-v3.1.0)
  • @relayburn/cli-darwin-x64@3.1.0 (tag: cli-darwin-x64-v3.1.0)
  • @relayburn/cli-linux-arm64-gnu@3.1.0 (tag: cli-linux-arm64-gnu-v3.1.0)
  • @relayburn/cli-linux-x64-gnu@3.1.0 (tag: cli-linux-x64-gnu-v3.1.0)
  • @relayburn/sdk-darwin-arm64@3.1.0 (tag: sdk-darwin-arm64-v3.1.0)
  • @relayburn/sdk-darwin-x64@3.1.0 (tag: sdk-darwin-x64-v3.1.0)
  • @relayburn/sdk-linux-arm64-gnu@3.1.0 (tag: sdk-linux-arm64-gnu-v3.1.0)
  • @relayburn/sdk-linux-x64-gnu@3.1.0 (tag: sdk-linux-x64-gnu-v3.1.0)

Crates

Release Notes

Added

  • burn update: upgrade to the latest release through whichever package manager installed the binary (npm or cargo); --check reports availability without installing.
  • On-launch update check: interactive burn invocations offer to install a newer release and restart, throttled to one network probe per 24h and suppressed once a version is declined.
  • burn update toggle-auto-update [--on|--off]: enable or disable the on-launch update check (state stored in $RELAYBURN_HOME/update.json).

Package Changelogs

relayburn

  • burn update now upgrades npm installs through npm install -g relayburn@latest: the launcher tags the install channel so the binary picks the right package manager.

Don't miss a new burn release

NewReleases is sending notifications on new releases.