Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

Notable changes to Swarmail. Versions follow [semantic versioning](https://semver.org).

## Unreleased
## 0.5.2 - 2026-10-09

- Require agents to record whole-session closeouts and retire their own project
registrations, with read-only verification and task/pause boundaries.
Expand All @@ -11,6 +11,9 @@ Notable changes to Swarmail. Versions follow [semantic versioning](https://semve
worktree that is gone, so the hook warned on every prompt until the session ended. The pending entry is dropped;
the session's next edit registers it again.

- The release check fails for a package that has no row in the listings section of
`CONTRIBUTING.md`, so a new package cannot ship without a listing decision.

## 0.5.1 - 2026-10-09

- A session whose usual name is already held by another session in a project
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -267,7 +267,7 @@ registering a second one. Where another session already holds that name in the p
`sdk-cli` registers on its first edit instead, so a read-only one-shot run adds no agent. A
child that inherited `sdk-ts` from an SDK-hosted session still registers at start. The registration starts with a tag
holding the host's session id and working directory, which is how `swarmail
who` matches names to sessions. A failure is retried on the next prompt or edit. State
who` matches names to sessions. A failure is retried on the next prompt or edit; a retry for an edit checkout that has since been deleted is dropped. State
lives in `~/.local/state/swarmail-register/`, under your profile on Windows.
After upgrading, run `bun scripts/configure-hooks.ts` again to add the
session-start hook.
Expand Down Expand Up @@ -342,7 +342,7 @@ wake an idle session.

Measured on 2026-10-04 at
[`67e187a`](https://github.com/bompus/swarmail/tree/67e187a6b4beb7319c6ab30466448742297e2a01).
These results have not been remeasured for 0.4.0, 0.5.0 or 0.5.1.
These results have not been remeasured for 0.4.0, 0.5.0, 0.5.1 or 0.5.2.
The measurements used one machine with one small workload (40 agents, 250 seed messages,
1,560 messages by the end). Each server started on empty storage. Startup is
hyperfine's mean of 20 runs; every other number is the median of three rounds,
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "swarmail",
"version": "0.5.1",
"version": "0.5.2",
"private": true,
"description": "Local mail, roster and file reservations for coding-agent sessions on one machine, served over MCP.",
"license": "MIT",
Expand Down
2 changes: 1 addition & 1 deletion packages/mcp-relay/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "swarmail-mcp",
"version": "0.5.1",
"version": "0.5.2",
"description": "Stdio MCP relay to a running Swarmail server, for MCP clients that install servers from a registry.",
"keywords": [
"coding-agents",
Expand Down
4 changes: 2 additions & 2 deletions server.json
Original file line number Diff line number Diff line change
Expand Up @@ -8,12 +8,12 @@
"source": "github"
},
"websiteUrl": "https://github.com/bompus/swarmail#install",
"version": "0.5.1",
"version": "0.5.2",
"packages": [
{
"registryType": "npm",
"identifier": "swarmail-mcp",
"version": "0.5.1",
"version": "0.5.2",
"runtimeHint": "npx",
"transport": {
"type": "stdio"
Expand Down
Loading