ci: use shared org-level Maven Central and signing secrets#970
Draft
nielspardon wants to merge 1 commit into
Draft
ci: use shared org-level Maven Central and signing secrets#970nielspardon wants to merge 1 commit into
nielspardon wants to merge 1 commit into
Conversation
Switch the release and sanity-check workflows to the org-level secrets shared with substrait-packaging, replacing the expired repo-level signing key and the old Sonatype credentials: - M2_CENTRAL_USERNAME / M2_CENTRAL_PASSWORD - M2_SIGNING_KEY_ID / M2_SIGNING_PASSWORD / M2_SIGNING_KEY Also fix the sanity workflow to export MAVENCENTRAL_USERNAME/PASSWORD (the names sanity.sh actually reads) instead of the unused SONATYPE_* vars, trim the semantic-release branches to main, and refresh ci/release/README.md for the new signing key and Central Portal (new fingerprint, repo1.maven.org URLs, and removal of outdated screenshots and stale snapshot/staging/OSSRH content).
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.
Switch the release and sanity-check workflows to the org-level secrets shared with the
substrait-packagingrepository, replacing the expired repo-level signing key (the previous Maven Central signing key expired in 2023) and the old Sonatype credentials:M2_CENTRAL_USERNAME/M2_CENTRAL_PASSWORDM2_SIGNING_KEY_ID/M2_SIGNING_PASSWORD/M2_SIGNING_KEYThis also:
MAVENCENTRAL_USERNAME/MAVENCENTRAL_PASSWORD— the namesci/release/sanity.shactually reads — instead of the previously unusedSONATYPE_*variables.semantic-releasebranches tomain(the only branch we release from).ci/release/README.mdfor the new signing key and the Sonatype Central Publisher Portal: new key fingerprint,repo1.maven.orgartifact URLs, and removal of outdated screenshots and stale snapshot/staging/OSSRH content.🤖 Generated with AI