[5.2.x] Migrate publishing to Central Publisher Portal

[jkasten2]

Description

One Line Summary

Migrate publishing from OSSRH to the Central Publisher Portal.

• There are no changes to those consuming this SDK, only for maintainers to publish.

Details

Added the plugin com.vanniktech.maven.publish to publish to the Central Publisher Portal.

To publish the following command must be used now:

./gradlew publishToMavenCentral --no-configuration-cache \
-PmavenCentralUsername=USER_TOKEN_USERNAME_HERE \
-PmavenCentralPassword=USER_TOKEN_PASSWORD_HERE \
-Psigning.keyId=ID_HERE \
-Psigning.password=PASSWORD_HERE \
-Psigning.secretKeyRingFile=/FULL/PATH/TO/GPG_FILE_HERE

Can switch to publishAndReleaseToMavenCentral once we do a release manually and test end-to-end.

Motivation

OSSRH is shutting down 2025/06/30 so we need to migrate to the Central Portal for publishing.

Scope

Only effects the logic used for publishing and releasing the SDK

Testing

Unit testing

N/A

Manual testing

Tested publishing validates default checks on the Central Portal dashboard:

Tested on the OneSignal example project before releasing a version:

• This only needs to be done if you are making major changes to the release process and want to to end-to-end before making the release public.

1. Bump version numbers in app/build.gradle

   • Example 5.2.0-beta-04 -> 5.2.0-beta-05

2. Add deployment repo in top level build.gradle

allprojects {
    repositories {
        maven {
            name = "centralManualTesting"
            url "https://central.sonatype.com/api/v1/publisher/deployment/{DEPLOYMENT_ID_HERE}/download"
            content {
                includeGroup "com.onesignal"
            }
            credentials(HttpHeaderCredentials)
            authentication {
                header(HttpHeaderAuthentication)
            }
        }
       // Keep existing entries
    }
}

3. Add auth to gradle.properties

centralManualTestingAuthHeaderName=Authorization

// To generate BASE64_VALUE use printf "example_username:example_password" | base64
centralManualTestingAuthHeaderValue=Bearer BASE64_VALUE

The instructions above were extracted from Central Portal testing docs:

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed
• All automated tests pass, or I explained why that is not possible
  • Pre-existing error
• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
  • Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
• I have reviewed this PR myself, ensuring it meets each checklist item
  • WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.

---

This change is 

[jinliu9508]

Approved. There is a failing test in the runner but can be resolved after a rebase.

[jkasten2]

Approved. There is a failing test in the runner but can be resolved after a rebase.

Thanks, rebased and it is now passing