ci: verify release secrets before deploy#2185
Open
zeitlinger wants to merge 5 commits into
Open
Conversation
Replaces debug step with explicit checks for Sonatype token, GPG key import, and GPG passphrase. Each failure points at the matching RELEASING.md section so the fix is clear from the workflow log. Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
zeitlinger
force-pushed
the
verify-release-secrets
branch
from
80e565a to
f8f679c
Compare
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
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
1 participant
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.
Summary
Debug gpg keystep with explicit checks for Sonatype token, GPG key import, and GPG passphrase match.RELEASING.mdsection.If the Sonatype Central Token is Invalidsection toRELEASING.md.Context: recent release attempt failed with
403on Maven Central upload because the user token was stale. The token mismatch was only visible deep in Maven output.Note: Also fixes zizmor - I'm still investigating why flint didn't catch this before
Test plan