Skip to content

RUM-10626: Migrate publishing from OSSRH to Central Publisher portal#2770

Merged
0xnm merged 1 commit into
developfrom
nogorodnikov/rum-10626/migrate-android-sdk-publication-to-central-publisher-portal
Jul 1, 2025
Merged

RUM-10626: Migrate publishing from OSSRH to Central Publisher portal#2770
0xnm merged 1 commit into
developfrom
nogorodnikov/rum-10626/migrate-android-sdk-publication-to-central-publisher-portal

Conversation

@0xnm

@0xnm 0xnm commented Jun 30, 2025

Copy link
Copy Markdown
Member

What does this PR do?

This PR moves away from the legacy OSSRH portal which is going to be sunset on June, 30th to the Central Publisher portal.

Announcement: https://central.sonatype.org/news/20250326_ossrh_sunset/

The desciption of the approach can be found in the code comments:

//see https://github.com/gradle-nexus/publish-plugin#publishing-to-maven-central-via-sonatype-central
// For official documentation:
// staging repo publishing https://central.sonatype.org/publish/publish-portal-ossrh-staging-api/#configuration
// snapshot publishing https://central.sonatype.org/publish/publish-portal-snapshots/#publishing-via-other-methods

We are not moving to the new publishing plugin which supports new Central Publisher portal directly (there is no first-party support in Gradle yet, so 3rd party needs to be used), but simply changing the URLs to target intermediate APIs.

I tested with Snapshots, it is working fine. Testing with staging repo for the release TBD.

Staging Profile ID is removed, because we don't know the new one yet (having it just makes publication faster, skipping some calls).

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Make sure you discussed the feature or bugfix with the maintaining team in an Issue
  • Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

@0xnm
0xnm force-pushed the nogorodnikov/rum-10626/migrate-android-sdk-publication-to-central-publisher-portal branch 2 times, most recently from dd4d88a to d9677f7 Compare June 30, 2025 12:59
@0xnm
0xnm force-pushed the nogorodnikov/rum-10626/migrate-android-sdk-publication-to-central-publisher-portal branch from d9677f7 to 2d06081 Compare June 30, 2025 14:02
@codecov-commenter

codecov-commenter commented Jun 30, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.85%. Comparing base (208da2c) to head (2d06081).
Report is 2 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #2770      +/-   ##
===========================================
+ Coverage    69.79%   69.85%   +0.06%     
===========================================
  Files          824      824              
  Lines        30877    30877              
  Branches      5196     5196              
===========================================
+ Hits         21548    21567      +19     
+ Misses        7852     7847       -5     
+ Partials      1477     1463      -14     

see 32 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@0xnm
0xnm marked this pull request as ready for review June 30, 2025 14:53
@0xnm
0xnm requested review from a team as code owners June 30, 2025 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants