Skip to content

The docs say what actually shipped - #101

Merged
sepehr-safari merged 1 commit into
mainfrom
docs-say-what-shipped
Sep 7, 2026
Merged

sepehr-safari merged 1 commit into
mainfrom
docs-say-what-shipped

Conversation

@sepehr-safari

@sepehr-safari sepehr-safari commented Sep 7, 2026 •

Copy link
Copy Markdown
Contributor

Four things a stranger reads first, each of them wrong.

The Quickstart fetched v0.12.0. That is the one copy-pasteable line in the README, the command a reader from a package list or a forum actually runs, and it silently handed them a version two releases old without the Relay.deinit leak fix that 0.14.1 exists for. The status line four lines above it already said 0.14.1.

CURRENT_STATE.md said v0.5.0 / v0.3.0 / v0.2.0. Ten, seven and sixteen releases behind, in the file the README sends people to for "exactly what's in progress". It also called Notary macOS-only on the day Linux tarballs shipped, and named notifications as the next milestone when notifications have been in Plaza for months.

So the version numbers come out of that file entirely. It went nine releases stale saying them, and a stale number is worse than no number: it is readable, specific and wrong. It links to each project's releases page instead, which cannot drift. What stays is the description of what exists, which changes slowly.

Both apps were described as macOS-only in the README's own "Built with it" section, on the day both shipped Linux builds.

Also here

Fixed AGENTS.md and CONTRIBUTING.md, and while in AGENTS.md the dependency graph is corrected. It listed karlseguin/websocket.zig and allyourcodebase/lmdb as planned. LMDB has been a real dependency since the store landed, and the websocket is not a dependency at all: src/websocket.zig implements RFC 6455 here, because the relay connection needs control over when a frame surfaces and no client library exposed that. The repository layout block listed three files when there are twenty-four.

No code changed, so no release is needed for this.

Four things a stranger reads first, each of them wrong.

The Quickstart's one copy-pasteable line fetched v0.12.0. That is the command a
reader from a package list or a forum actually runs, and it silently handed them
a version two releases old, without the leak fix 0.14.1 exists for. The status
line four lines above it already said 0.14.1.

`CURRENT_STATE.md`, which the README sends people to for "exactly what's in
progress", said the library was v0.5.0, Notary v0.3.0 and Plaza v0.2.0. Ten,
seven and sixteen releases behind. It also called Notary macOS-only on the day
Linux tarballs shipped, and named notifications as the next milestone when
notifications have been in Plaza for months.

So the version numbers come out of that file entirely. It went nine releases
stale saying them, and a stale number is worse than no number: it is readable,
specific and wrong. It links to each project's releases instead, which cannot
drift. What stays is the description of what exists, which changes slowly.

Both apps were described as macOS-only in the README's own "Built with it"
section, on the day both shipped Linux builds.

Also here: the em-dashes are gone from AGENTS.md and CONTRIBUTING.md, and while
in AGENTS.md the dependency graph is corrected. It listed `karlseguin/websocket.zig`
and `allyourcodebase/lmdb` as PLANNED. LMDB has been a real dependency since the
store landed, and the websocket is not a dependency at all: `src/websocket.zig`
implements RFC 6455 here, because the relay connection needs control over when a
frame surfaces. The repository layout block listed three files when there are
twenty-four.

The CHANGELOG's em-dashes are left alone deliberately. Those entries are the
published text of past releases, and editing them here would only make the file
disagree with the release pages.
@sepehr-safari
sepehr-safari merged commit 8be531e into main Sep 7, 2026
2 checks passed
@sepehr-safari
sepehr-safari deleted the docs-say-what-shipped branch September 7, 2026 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant