[undecuple]

Why

v0.6.0 is published (2026-11-13 UTC, pre-release) and its container image ghcr.io/undecuple/re-psn:0.6.0 is in the registry, but the README and docker/README.md still name v0.5.0 as the newest, and four rows of docs/features.tsv still say since = main, which means "merged but not released". This is step 9 of docs/releasing.md.

Change

• README.md: the "newest" release link, its image name, the Container paragraph (docker pull ghcr.io/undecuple/re-psn:0.6.0; 0.5.0, 0.4.0, 0.3.0 and 0.2.0 are still there), the release box above the archive list and the "current release is" remark in the captured-run note now say v0.6.0 / 0.6.0. The sentence that says what v0.5.0 added, and the "not in v0.5.0" notes in the settings table, are left as they are: they are still true.
• docker/README.md: the current image and the docker pull line say 0.6.0.
• docs/features.tsv: since changes from main to 0.6.0 for net-no-peer-titles, net-caps, client-connect-policy and admin-api. docs-website stays at main (the site is deployed from main and is not a release asset). The admin-api row's note said "Experimental and not in a release."; that is no longer true, so it now says "Experimental, first in v0.6.0." and the rest of the note is unchanged. The other three rows' notes ("Not in v0.5.0") stay true. docs/features.md and site/ regenerated.
• CHANGELOG: a Docs and tooling: entry under a new [Unreleased] / Changed.

Tests

• Each of the four rows was checked against the v0.6.0 tag and against v0.5.0: git grep at the tag finds no-peer-titles in server/main.go, msgGetCaps in server/caps.go and server/server.go, psnr_set_connect_policy in client/psnr.h and admin-read-token-file in server/main.go; none of them is in the v0.5.0 tree (server/caps.go does not exist there); each is named in the CHANGELOG [0.6.0] section and in no earlier section.
• The image exists: the registry answers 200 for the 0.6.0 manifest (linux/amd64 and linux/arm64) and lists tags 0.2.0 to 0.6.0; 0.6 and latest do not exist, as for any pre-release.
• python3 tools/features.py, python3 tools/site.py --check, python3 tools/repo_check.py, scripts/check-deploy.sh, python3 -m unittest tools.test_site and the server version and release tests pass. The Go suite as a whole is left to CI.
• Counts by since after the change: 3 at 0.1.0, 26 at 0.2.0, 2 at 0.3.0, 7 at 0.4.0, 12 at 0.5.0, 4 at 0.6.0, 1 at main, 25 empty.

Not in this change

The docs/releasing.md text, the installers and the website's layout are unchanged. No tag, no release.

Overlap

None open.

Developed with AI agent assistance.