Release workflows: use ASF org-shared Nexus deployer secret names - #3776
Merged
Conversation
Nexus staging deploys returned HTTP 401 because the release workflows read secrets.PARQUET_NEXUS_USER / PARQUET_NEXUS_PASSWORD, which don't exist on apache/parquet-java. ASF Infra shares the deployer credentials at the org level under NEXUS_STAGE_DEPLOYER_USER / NEXUS_STAGE_DEPLOYER_PW. Point the workflows at those names so the env vars are populated and Nexus accepts the upload. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Fokko
approved these changes
Sep 5, 2026
Contributor
|
Thanks for following up here @RussellSpitzer 🙌 |
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
2 participants
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.
Rationale for this change
Nexus secret names were incorrect - Infra gave us different secrets than I thought
What changes are included in this PR?
Secret names are changed
Are these changes tested?
No, only an ADMIN can actually see the secrets on this repo
Are there any user-facing changes?
No