Publish SNAPSHOT versions to GitHub Packages instead of Maven Central

[AlvaroBrey]

WIP

---

Note

Medium Risk
Changes artifact distribution for every snapshot deploy and consumer repo config; release paths are gated on version suffix and Central tasks are disabled for snapshots, but CI credential or task misconfiguration could break mainline snapshot publishing.

Overview
-SNAPSHOT builds now publish to GitHub Packages instead of Maven Central; release publishing is unchanged.

Gradle convention adds configureSnapshotPublishing() for public library modules: when VERSION_NAME ends in -SNAPSHOT, it registers https://maven.pkg.github.com/RevenueCat/purchases-android and disables Maven Central publish tasks so snapshots cannot ship to Central.

Fastlane deploy picks credentials and Gradle publish tasks by version—snapshots use publishAllPublicationsToGitHubPackagesRepository with GitHub Packages env vars and skip GitHub release creation; releases still use Maven Central and publish.

CircleCI snapshot workflows add the github-packages-publishing context for deploy and for sample apps that resolve snapshot dependencies after deploy. Example apps switch their snapshot Maven repo from Sonatype to GitHub Packages with the same credential properties/env vars.

RELEASING.md documents snapshot behavior, PAT scopes, and consumer Gradle setup.

^{Reviewed by Cursor Bugbot for commit f57cba5. Bugbot is set up for automated code reviews on this repo. Configure here.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.27%. Comparing base (aff4907) to head (6754289).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3647   +/-   ##
=======================================
  Coverage   80.27%   80.27%           
=======================================
  Files         379      379           
  Lines       15557    15557           
  Branches     2170     2170           
=======================================
  Hits        12489    12489           
  Misses       2203     2203           
  Partials      865      865           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[AlvaroBrey]

Both contexts because we need the signing keys. We also could just not sign snapshots TBH.

[AlvaroBrey]

@cursor review pls

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f57cba5. Configure here.}

[cursor]

BOM and codegen skip snapshot publish

Medium Severity

configureSnapshotPublishing() is only invoked from the public library convention plugin, while :bom and :codegen apply com.vanniktech.maven.publish on their own. Snapshot deploy now runs publishAllPublicationsToGitHubPackagesRepository instead of publish, so purchases-bom and purchases-codegen-plugin are not published to GitHub and still have Maven Central publish tasks enabled.

Additional Locations (1)

• fastlane/Fastfile#L268-L279

 

^{Reviewed by Cursor Bugbot for commit f57cba5. Configure here.}

[AlvaroBrey]

Fixed