From dfa13bce339961e81ed673fa89e800b8154551db Mon Sep 17 00:00:00 2001
From: Louis-Arnaud <la.catoire@gmail.com>
Date: Sun, 16 Aug 2026 19:46:10 +0200
Subject: [PATCH] sodium_crypto_aead_aes256gcm_is_available: document 8.4
 aarch64 support

---
 ...ium-crypto-aead-aes256gcm-is-available.xml | 28 +++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/reference/sodium/functions/sodium-crypto-aead-aes256gcm-is-available.xml b/reference/sodium/functions/sodium-crypto-aead-aes256gcm-is-available.xml
index bc592dae462e..3a5e477561d4 100644
--- a/reference/sodium/functions/sodium-crypto-aead-aes256gcm-is-available.xml
+++ b/reference/sodium/functions/sodium-crypto-aead-aes256gcm-is-available.xml
@@ -30,6 +30,34 @@
   </simpara>
  </refsect1>
 
+ <refsect1 role="changelog">
+  &reftitle.changelog;
+  <informaltable>
+   <tgroup cols="2">
+    <thead>
+     <row>
+      <entry>&Version;</entry>
+      <entry>&Description;</entry>
+     </row>
+    </thead>
+    <tbody>
+     <row>
+      <entry>8.4.0</entry>
+      <entry>
+       This function may now return &true; on aarch64 CPUs that provide the
+       ARM cryptographic extensions (the ARMv8 AES instructions). Previously,
+       hardware-accelerated AES-256-GCM was only detected on x86 and x86-64
+       hardware: this function always returned &false; on aarch64, and the
+       other AES-256-GCM functions, such as
+       <function>sodium_crypto_aead_aes256gcm_encrypt</function>, were not
+       available on that platform at all.
+      </entry>
+     </row>
+    </tbody>
+   </tgroup>
+  </informaltable>
+ </refsect1>
+
 
 </refentry>
 <!-- Keep this comment at the end of the file