Attach the release AAR to the published Maven artifact

[brionmario]

Summary

• The release Maven publication declared a groupId/artifactId/version but never called from(components["release"]), so it published an empty POM shell with no .aar attached.
• Every consumer resolving this library via JitPack (com.github.thunder-id:android-sdks) got a packaging=pom artifact with zero compiled classes, regardless of which ref/commit/tag was requested — this broke any Gradle project trying to depend on a commit/branch snapshot (only the previously-published 0.1.0 release artifact happened to work, likely published before this regressed).
• Added android.publishing { singleVariant("release") } and wrapped the publication in afterEvaluate so components["release"] is available before from(...) references it.

Test plan

• ./gradlew publishReleasePublicationToMavenLocal succeeds
• Verified the produced android-0.1.0.aar in ~/.m2 actually contains classes.jar (previously it did not)
• CI build passes

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@brionmario, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 30 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 0f224811-5337-4205-b136-f768e41898a6

📥 Commits

Reviewing files that changed from the base of the PR and between a4b586c and 8dbc9ac.

📒 Files selected for processing (1)

• build.gradle.kts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}