Repository navigation
Releases: Wearer-Lab/agent-relay
Releases · Wearer-Lab/agent-relay
Release list
v0.7.3
Full Changelog: v0.7.2...v0.7.3
v0.7.2
What's Changed
Other changes
- ci: bump the actions group across 1 directory with 5 updates by @dependabot[bot] in #4
- deps: bump zod from 4.6.5 to 4.6.7 in the npm-minor-patch group across 1 directory by @dependabot[bot] in #5
New Contributors
- @dependabot[bot] made their first contribution in #4
Full Changelog: v0.7.1...v0.7.2
v0.7.1
v0.7.0
v0.6.0
v0.5.0
What's Changed
Other changes
- Port the test suite to Windows and require Windows CI by @spyhack225 in #6
- Batch broker writes, keep presence in memory, and add compaction by @spyhack225 in #7
- Release 0.5.0 by @spyhack225 in #8
Full Changelog: v0.4.0...v0.5.0
v0.4.0
What's Changed
Other changes
- Measure Windows swap from page file usage, not commit charge by @spyhack225 in #1
- Release 0.3.2 by @spyhack225 in #2
- Release 0.4.0: registry hygiene, branch ownership, roadmaps, dashboard redesign by @spyhack225 in #3
New Contributors
- @spyhack225 made their first contribution in #1
Full Changelog: v0.2.0...v0.4.0
v0.2.0
Agent Relay 0.2.0
Released 2026-10-05. This release adds backward-compatible coordination features.
- Poll inboxes with cursors and filters, acknowledge messages in bulk, and watch JSON lines with automatic reconnection after a broker restart.
- Coordinate machine-wide resource claims across project rooms, inspect holders and stale claims, and record explicit forced releases in the ledger.
- Inspect measured swap, load, and free disk with
agent-relay gate, and run gate checks before claiming resources. - Track last-seen presence, filter active or stale agents, and explicitly leave while retaining history and claims.
- Send durable local attachments, fetch authorized copies, and verify their hashes and sizes.
- Add short message summaries for inbox, watch, and dashboard previews.
Existing basic commands remain compatible. Restart an older broker to use the new options; messages and history remain in its existing data directory. Attachments remain local and are excluded from releases.
Validation uses isolated temporary storage: the full test suite, release package checks, the improvements smoke test, and npm publication dry run.