From 36bedb6c6afeb652ac75b72db634dde05af2797f Mon Sep 17 00:00:00 2001
From: babolivier <babolivier@users.noreply.github.com>
Date: Wed, 20 Oct 2021 11:04:56 +0000
Subject: deploy: 78d5896d19692e4b6cdbf09f807915e6b0929ce5

---
 develop/modules/account_validity_callbacks.html | 2 ++
 1 file changed, 2 insertions(+)

(limited to 'develop/modules/account_validity_callbacks.html')

diff --git a/develop/modules/account_validity_callbacks.html b/develop/modules/account_validity_callbacks.html
index 1d6d0a734d..0eabf60bb7 100644
--- a/develop/modules/account_validity_callbacks.html
+++ b/develop/modules/account_validity_callbacks.html
@@ -189,6 +189,7 @@ Synapse instance. Account validity callbacks can be registered using the module
 <code>register_account_validity_callbacks</code> method.</p>
 <p>The available account validity callbacks are:</p>
 <h3 id="is_user_expired"><a class="header" href="#is_user_expired"><code>is_user_expired</code></a></h3>
+<p><em>First introduced in Synapse v1.39.0</em></p>
 <pre><code class="language-python">async def is_user_expired(user: str) -&gt; Optional[bool]
 </code></pre>
 <p>Called when processing any authenticated request (except for logout requests). The module
@@ -203,6 +204,7 @@ callback returns <code>None</code>, Synapse falls through to the next one. The v
 callback that does not return <code>None</code> will be used. If this happens, Synapse will not call
 any of the subsequent implementations of this callback.</p>
 <h3 id="on_user_registration"><a class="header" href="#on_user_registration"><code>on_user_registration</code></a></h3>
+<p><em>First introduced in Synapse v1.39.0</em></p>
 <pre><code class="language-python">async def on_user_registration(user: str) -&gt; None
 </code></pre>
 <p>Called after successfully registering a user, in case the module needs to perform extra
-- 
cgit 1.5.1