Skip to content

fix(release): supply Maven Central creds as ORG_GRADLE_PROJECT_ props (qs-04) #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
abbaseya merged 1 commit into from
Jun 4, 2026
Merged

fix(release): supply Maven Central creds as ORG_GRADLE_PROJECT_ props (qs-04) #44

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,8 +125,13 @@ jobs:
# Sonatype Central Portal credentials. Generate these in the
# Central Portal UI (https://central.sonatype.com) → user tokens.
# See RELEASE.md §"Secrets" for the exact acquisition steps.
MAVEN_CENTRAL_USERNAME: ${{ secrets.MAVEN_CENTRAL_USERNAME }}
MAVEN_CENTRAL_PASSWORD: ${{ secrets.MAVEN_CENTRAL_PASSWORD }}
# Exposed as Gradle project properties (`mavenCentralUsername` /
# `mavenCentralPassword`) via the `ORG_GRADLE_PROJECT_` prefix —
# the same convention as the `ORG_GRADLE_PROJECT_signingInMemoryKey*`
# lines below. The vanniktech maven-publish plugin reads these
# properties to authenticate `publishToMavenCentral`. (qs-04.)
ORG_GRADLE_PROJECT_mavenCentralUsername: ${{ secrets.MAVEN_CENTRAL_USERNAME }}
ORG_GRADLE_PROJECT_mavenCentralPassword: ${{ secrets.MAVEN_CENTRAL_PASSWORD }}

# In-memory GPG signing key for vanniktech's plugin. Export the
# private key with `gpg --armor --export-secret-keys <KEY_ID>`
Expand Down
Loading