Release 2.21.1.

CHANGELOG.rst

@@ -4,6 +4,19 @@ Community Crypto Release Notes
 
 .. contents:: Topics
 
+v2.21.1
+=======
+
+Release Summary
+---------------
+
+Maintenance release.
+
+Bugfixes
+--------
+
+- When using cryptography >= 43.0.0, use offset-aware ``datetime.datetime`` objects (with timezone UTC) instead of offset-naive UTC timestamps for the ``InvalidityDate`` X.509 CRL extension (https://github.com/ansible-collections/community.crypto/issues/726, https://github.com/ansible-collections/community.crypto/pull/730).
+
 v2.21.0
 =======
 

changelogs/changelog.yaml

@@ -1465,3 +1465,15 @@ releases:
       - 779-add-tls_ctx_options-option.yml
       - 784-get_certificate-get_certificate_chain.yml
     release_date: '2024-07-12'
+  2.21.1:
+    changes:
+      bugfixes:
+        - When using cryptography >= 43.0.0, use offset-aware ``datetime.datetime``
+          objects (with timezone UTC) instead of offset-naive UTC timestamps for the
+          ``InvalidityDate`` X.509 CRL extension (https://github.com/ansible-collections/community.crypto/issues/726,
+          https://github.com/ansible-collections/community.crypto/pull/730).
+      release_summary: Maintenance release.
+    fragments:
+      - 2.21.1.yml
+      - 730-cryptography-invalidity_date.yml
+    release_date: '2024-07-21'

changelogs/fragments/2.21.1.yml

@@ -1 +0,0 @@
-release_summary: Maintenance release.

changelogs/fragments/730-cryptography-invalidity_date.yml

@@ -1,2 +0,0 @@
-bugfixes:
-  - When using cryptography >= 43.0.0, use offset-aware ``datetime.datetime`` objects (with timezone UTC) instead of offset-naive UTC timestamps for the ``InvalidityDate`` X.509 CRL extension (https://github.com/ansible-collections/community.crypto/issues/726, https://github.com/ansible-collections/community.crypto/pull/730).