You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For many years LmdbJava artifacts have been signed using my personal CI server code signing GPG key ID 31760922FB4ED1A8.
To support multiple committers on the project (#254) I have created a new GPG key specifically for LmdbJava.
Going forward LmdbJava releases will be signed with GPG key ID 0B0DB769E1917B61.
Please follow the above links to view full key details, including possible future revocation.
I am creating this issue primarily to assist those who may notice GPG signatures on Maven Central artifacts have changed and require a public confirmation of the change.
For many years LmdbJava artifacts have been signed using my personal CI server code signing GPG key ID 31760922FB4ED1A8.
To support multiple committers on the project (#254) I have created a new GPG key specifically for LmdbJava.
Going forward LmdbJava releases will be signed with GPG key ID 0B0DB769E1917B61.
Please follow the above links to view full key details, including possible future revocation.
I am creating this issue primarily to assist those who may notice GPG signatures on Maven Central artifacts have changed and require a public confirmation of the change.
cc: @stroomdev66 @at055612