The banner on tangled.org flags my self-hosted knot (knot.ohc.network) as out of date and needing an upgrade.
While knot-unwrapped pins the version to 1.11-alpha, I manually overrode this to 1.13-alpha and successfully upgraded. However, the banner persists.
Checking the versions via the API makes this even stranger — my knot is actually running a newer version than the one managed by the Tangled team:
$ curl https://knot1.tangled.sh/xrpc/sh.tangled.knot.version
{"version":"1.11.0-alpha"}
$ curl https://knot.ohc.network/xrpc/sh.tangled.knot.version
{"version":"1.13.0-alpha"}
knot1.tangled.sh (the Tangled-managed knot) is on 1.11.0-alpha, yet my knot at 1.13.0-alpha is the one being flagged as outdated. It seems like the banner logic may be comparing against a hardcoded or incorrectly sourced version number rather than the actual latest version.