Skip to content

docs: fold the unreleased notes into 0.5.2 and align the benchmark remeasure line #128

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bompus merged 1 commit into from
Oct 10, 2026
Merged

docs: fold the unreleased notes into 0.5.2 and align the benchmark remeasure line #128

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
22 changes: 10 additions & 12 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,18 +2,6 @@

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

## Unreleased

- `swarmail who` asks git about each running T3 thread directory once instead of once per thread. With about 800
running threads in 149 directories it took 0.3 s instead of 1.6 s.

- `fetch_inbox` and `fetch_session_inbox` no longer read each message body from storage when `include_bodies` is off,
which is the default. A page of 20 messages took 48 µs instead of 57 µs with 2 KB bodies and 52 µs instead of 82 µs
with 17 KB bodies.

- The `swarmail-mcp` README lists the memory each launch command costs: about 180 MiB for `npx -y swarmail-mcp`, 82 MiB
for `bunx swarmail-mcp` and 46 MiB for `bunx --bun swarmail-mcp`, which runs the same relay under Bun.

## 0.5.2 - 2026-10-09

- Require agents to record whole-session closeouts and retire their own project
Expand All @@ -26,6 +14,16 @@ Notable changes to Swarmail. Versions follow [semantic versioning](https://semve
- 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.

- `swarmail who` asks git about each running T3 thread directory once instead of once per thread. With about 800
running threads in 149 directories it took 0.3 s instead of 1.6 s.

- `fetch_inbox` and `fetch_session_inbox` no longer read each message body from storage when `include_bodies` is off,
which is the default. A page of 20 messages took 48 µs instead of 57 µs with 2 KB bodies and 52 µs instead of 82 µs
with 17 KB bodies.

- The `swarmail-mcp` README lists the memory each launch command costs: about 180 MiB for `npx -y swarmail-mcp`, 82 MiB
for `bunx swarmail-mcp` and 46 MiB for `bunx --bun swarmail-mcp`, which runs the same relay under Bun.

## 0.5.1 - 2026-10-09

- A session whose usual name is already held by another session in a project
Expand Down
2 changes: 1 addition & 1 deletion docs/benchmarks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ The results cover this workload only. They say nothing about durability after
a crash, large archives or production load.
Swarmail was measured at
[`67e187a`](https://github.com/bompus/swarmail/tree/67e187a6b4beb7319c6ab30466448742297e2a01).
These results have not been remeasured for 0.4.0.
These results have not been remeasured for 0.4.0, 0.5.0, 0.5.1 or 0.5.2.

## Summary

Expand Down
Loading