fix(publishing): restore Maven Central publishing for isolated kits - #753
Conversation
Move Maven publication conventions into shared build logic so isolated Kotlin kit builds expose the same Central publishing tasks as root builds. Validate core, aggregate, and isolated artifacts in Maven Local before uploading them, and pin isolated kit dependencies to the release version. #agentic
PR SummaryMedium Risk Overview Release safety: POM validation now runs before Maven Central uploads (not only Docs and README tables are updated for the new coordinates and Reviewed by Cursor Bugbot for commit 22aff9a. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort 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 01ea777. Configure here.

Background
The 6.0.1 release workflow attempted to publish four Kotlin-isolated kits from
their standalone Gradle roots. Those builds could not access the root-only
buildSrcpublication convention, so the Maven Central publication task wasnot registered and the isolated artifacts were not published.
What Has Changed
buildSrcinto sharedbuild-logicthat is available to root, aggregate-kit, and standalone-kitbuilds.
urbanairship-20,braze-43,ga-23, andga4-23.smoke tests before uploading release artifacts.
Maven Central uploads.
post-release verification process.
Screenshots/Video
N/A — build and release workflow changes only.
Checklist