diff --git a/CHANGELOG b/CHANGELOG
index b84c2e9f29..36397dbfa9 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -1,4 +1,4 @@
-git-annex (10.20240702) UNRELEASED; urgency=medium
+git-annex (10.20240731) UNRELEASED; urgency=medium
 
   * New HTTP API that is equivilant to the P2P protocol.
   * annex+http and annex+https urls can be configured for
diff --git a/doc/tips/smart_http_server.mdwn b/doc/tips/smart_http_server.mdwn
index d7a56d0596..54264e3499 100644
--- a/doc/tips/smart_http_server.mdwn
+++ b/doc/tips/smart_http_server.mdwn
@@ -3,8 +3,8 @@ as shown in the tip [[setup_a_public_repository_on_a_web_site]].
 
 That's limited to basic read-only repository access though. Git
 has [smart HTTP](https://git-scm.com/book/en/v2/Git-on-the-Server-Smart-HTTP)
-that can be used to allow pushes over http. And git-annex has an
-equivilant, the [[git annex-p2phttp command|/git-annex-p2phttp]].
+that can be used to allow pushes over http. And git-annex
+has the [[git annex-p2phttp command|/git-annex-p2phttp]].
 
 As well as allowing write access to authorized users over http,
 `git-annex p2phttp` also allows accessing [[clusters]], and other proxied
@@ -37,3 +37,7 @@ In the git config file of the repository, set `annex.url` to the "annex+http"
 (or "annex+https") url. The first time it uses a http remote, git-annex
 downloads its git config file, and sets `remote.name.annexUrl` to the value
 of the remote's `annex.url`.
+
+Support for this first appeared in git-annex version 10.20240731. Users of
+older git-annex won't be able to use the smart http server, but can still
+clone the repository from the dumb http server.