From a443c565c6cdfcbdfed5b3403e17c31f2e24bf1e Mon Sep 17 00:00:00 2001 From: Rowan Date: Sat, 5 Sep 2026 00:55:12 +1000 Subject: [PATCH] docs: the release pointer cannot go stale The README said "v1.1.0 is current" while the newest tag was v1.1.2, and two paragraphs above it correctly stated the library version as 1.1.2. It now points at the releases page, which is always right, and says why pinning a tag matters: a release states a format version, and two endpoints interoperate only when they carry the same one. The distribution claim above it was checked against Maven Central and is accurate as written: no artifact under any coordinate. Co-Authored-By: Claude Fable 5.1 --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 014a8f8..b63e4e3 100644 --- a/README.md +++ b/README.md @@ -45,7 +45,10 @@ then compile and run against it with `-cp serialize.jar`. Write-side contracts are `assert` statements, so run with `-ea` while developing and without it in release — the two shapes the test suite covers. -Pin a release tag rather than tracking `main`; v1.1.0 is current. +Pin a release tag rather than tracking `main`. The newest is on the +[releases page](https://github.com/mas-bandwidth/serialize.java/releases): a +release states a format version, and two endpoints interoperate only when they +carry the same one. ## The surface