core: New flag fields beta_compliance.

* src/gpgme.h.in (struct _gpgme_subkey): Add field beta_compliance.
(struct _gpgme_op_decrypt_result): Ditto.
(struct _gpgme_signature): Ditto.
* src/util.h (PARSE_COMPLIANCE_FLAGS): Handle the new 2023 value.
* tests/run-decrypt.c: Append a "(beta)" to the vs-de compliance.
* tests/run-keylist.c: Ditto.
* tests/run-verify.c: Ditto.
--

See GnuPG commit b287fb577587655559fefb90f7ed90c9a15dc6a3

1 files changed, 10 insertions, 0 deletions

diff --git a/doc/gpgme.texi b/doc/gpgme.texi
index 0e64254b..004d66ba 100644
--- a/doc/gpgme.texi
+++ b/doc/gpgme.texi
@@ -3645,6 +3645,11 @@ information in Germany at the restricted level (VS-NfD).  This are
 currently RSA keys of at least 2048 bits or ECDH/ECDSA keys using a
 Brainpool curve.
 
+@item unsigned int beta_complinance : 1;
+@since{1.24.0}
+The compliance flags (e.g. is_de_vs) are set but the software has not
+yet been approved or is in a beta state.
+
 @item unsigned int secret : 1
 This is true if the subkey is a secret key.  Note that it will be
 false if the key is actually a stub key; i.e., a secret key operation
@@ -5900,6 +5905,11 @@ The message claims that the content is a MIME object.
 The message was encrypted in a VS-NfD compliant way.  This is a
 specification in Germany for a restricted communication level.
 
+@item unsigned int beta_complinance : 1;
+@since{1.24.0}
+The compliance flags (e.g. is_de_vs) are set but the software has not
+yet been approved or is in a beta state.
+
 @item gpgme_recipient_t recipients
 @since{1.1.0}