This is relevant for the update check in Gpg4win.
Example:
$ gpgconf --query-swdb gpg4win 3.1.16-beta16 gpg4win:3.1.16-beta16:n::0:20211012T161328:20211019T103252:3.1.16:20210611T000000:0::
-> Although 3.1.16 is available gpgconf --query-swdb claims n, i.e. "The installed version [3.1.16-beta16] is already newer than the released version [3.1.16]." Obviously, that's incorrect.
For comparison, the following works correctly:
$ gpgconf --query-swdb gpg4win 3.1.17 gpg4win:3.1.17:n::0:20211012T161328:20211019T103252:3.1.16:20210611T000000:0::
-> Yes, 3.1.17 is newer than 3.1.16.
$ gpgconf --query-swdb gpg4win 3.1.16 gpg4win:3.1.16:c::0:20211012T161328:20211019T103252:3.1.16:20210611T000000:0::
-> Yes, 3.1.16 is the current version.
$ gpgconf --query-swdb gpg4win 3.1.15-beta16 gpg4win:3.1.15-beta16:u::0:20211012T161328:20211019T103252:3.1.16:20210611T000000:0::
-> Yes, 3.1.15-beta16 is older than 3.1.16.