This tag is used as a reminder to do a release and to collect information pertaining to such a release. It is often useful to add this bug number to release information so that users are able to quickly find solutions for problems with a certain release.
Details
Tue, Oct 7
Wed, Oct 1
Tue, Sep 23
Sep 5 2025
For the full fledged Windows installer see https://files.gpg4win.org/Beta/gpg4win-5.0.0-beta369/gpg4win-5.0.0-beta369.exe
Sep 2 2025
Aug 4 2025
1.11.2 has been release see T7642
Release done.
Jul 31 2025
Jul 30 2025
Note that 2.5.11 fixes a regression in 2.5.10 regarding the use of notations for 3rd party signatures. See T7743
Jul 28 2025
Noteworthy changes in version 1.3.2 (2025-07-28)
Jul 25 2025
Jul 18 2025
I wonder about GCC 15 preparation for the release. If it's good to have, three patches are needed to apply:
- Cherry-picking rCd5fb7cd9b351: Mark nonstring use cases with __nonstring__ attribute.
- strictly speaking, this adds a macro, which is considered an API change
- Cherry-picking rCf06e90f4137a: cipher:ecc: Silence GCC 15 warning.
- Apply changes of T7721: libgcrypt build-error with gcc-15 on powerpc and alpha
Jul 16 2025
Jul 14 2025
Jul 10 2025
701bd8fe8789a86cd2b7c27254a2ab837ee4fcfa gnupg-2.5.9.tar.bz2 1209dd1dc3cb9e33e3c7857e7f10a7b0fc8d478e gnupg-w32-2.5.9_20250710.tar.xz 0c7814a9ed67c48d0498f42f5a0eeaaf18e29f49 gnupg-w32-2.5.9_20250710.exe
Jun 20 2025
In case of problems with token based cv25519 key, please update to 2.5.8.
Jun 17 2025
Jun 5 2025
We will keep the 1.24 branch for bug fixing. Do you really have a problem with gpgme 2.0? Ist that due to factoring out the c++ and qt bindings? That was actually a long standing request from the KDE community so that they can use their cmake stuff.
I'm wondering whether gpgme v1 will still be supported? Or it will be abandoned from now on.