[codex] Ensure PGP public key is available before Central release#13
Merged
Conversation
wk1995
added a commit
that referenced
this pull request
Jul 22, 2026
[codex] Ensure PGP public key is available before Central release
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Root cause
The Publish Plugin Central workflow uploaded artifacts to Central staging successfully, but Central Portal deployment failed because Sonatype could not find the public PGP key for the signatures:
Invalid signature ... Could not find a public key by the key fingerprint.Sonatype requires the signing public key to be distributed to a supported keyserver before Central can validate signed artifacts.
Summary
.github/scripts/ensure_pgp_public_key_available.pyto import the CI signing key into a temporary GPG home, extract the primary fingerprint, publish the public key tokeyserver.ubuntu.com, and verify it can be fetched from a separate keyring.publish-plugin-central.ymlbefore publishing to Central staging.Validation
python3 -m unittest discover -s .github/scripts -p '*_test.py'./gradlew :plugin_base:build --stacktrace./gradlew :plugin_base:publishToMavenLocal --stacktracepython3 .github/scripts/validate_publish_plugin_publications.py./gradlew :plugin_base:publishAllPublicationsToCentralStagingRepository -PcentralPublish=true --dry-run --stacktrace