chore: Moving from OSSRH to the Maven Central Portal to publish the SDK library release.#276
chore: Moving from OSSRH to the Maven Central Portal to publish the SDK library release.#276mrudatsprint wants to merge 23 commits intomainfrom
Conversation
…-main' into release-please--branches--main
mrudatsprint
changed the title
| role-session-name: aws-auth-action | ||
| aws-region: ${{ env.AWS_REGION }} | ||
|
|
||
| - name: get secrets into the env |
There was a problem hiding this comment.
Get the secrets from AWS to publish the artifact to the Central Portal.
There was a problem hiding this comment.
Pull request overview
Migrates the Android SDK release publishing pipeline from legacy OSSRH staging to Sonatype’s Maven Central Portal workflow, aligning with OSSRH EOL timelines.
Changes:
- Updates Gradle publishing configuration to publish artifacts to a local build directory (for bundling/upload).
- Updates the main release workflow to trigger the new Central Portal publish workflow.
- Adds a new
release-publish.ymlworkflow to bundle and upload artifacts to Maven Central Portal; removes the old OSSRH workflow.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
library/build.gradle.kts |
Replaces OSSRH publish target with a local maven directory repository for later bundling. |
.github/workflows/release.yml |
Switches the triggered publish workflow from OSSRH to the new Central Portal workflow. |
.github/workflows/release-publish.yml |
New workflow that builds/signs locally, zips the repo output, and uploads to Central Portal. |
.github/workflows/release-publish-ossrh.yml |
Removes obsolete OSSRH-based publishing workflow. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| run: | | ||
| RESPONSE=$(curl --request POST \ | ||
| --verbose \ | ||
| --user '${{ env.CENTRAL_USERNAME }}:${{ env.CENTRAL_PASSWORD }}' \ |
There was a problem hiding this comment.
The Central Portal credentials are populated at runtime via $GITHUB_ENV in a previous step, but ${{ env.CENTRAL_USERNAME }} / ${{ env.CENTRAL_PASSWORD }} are evaluated as GitHub expressions before the step runs, so they may be empty here. Use the shell env vars ($CENTRAL_USERNAME / $CENTRAL_PASSWORD) instead so the values set from AWS Secrets Manager are actually used.
| --user '${{ env.CENTRAL_USERNAME }}:${{ env.CENTRAL_PASSWORD }}' \ | |
| --user "$CENTRAL_USERNAME:$CENTRAL_PASSWORD" \ |
There was a problem hiding this comment.
No, CENTRAL_USERNAME and CENTRAL_PASSWORD are set in the environment when retrieving the secrets by executing aws secretsmanager get-secret-value
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
2 participants
Moving from OSSRH to the Maven Central Portal to publish the SDK library release. OSSRH was end of life June 30, 2025