Skip to content

Upgrade Android build tools to API 36 - #4

Merged
BenjaminAmos merged 3 commits into
mainfrom
android-build-tools-api-36
Jul 30, 2026
Merged

Upgrade Android build tools to API 36#4
BenjaminAmos merged 3 commits into
mainfrom
android-build-tools-api-36

Conversation

@BenjaminAmos

Copy link
Copy Markdown
Contributor

This is needed to deploy again to Google Play, if required at some point in the future.

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

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

Next review available in: 43 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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ae1e0481-2a60-498b-a875-11d14dc0293c

📥 Commits

Reviewing files that changed from the base of the PR and between 8425466 and a0748bc.

📒 Files selected for processing (1)
  • Dockerfile
📝 Walkthrough

Walkthrough

The Docker image’s Android SDK installation now targets build tools 36.0.2 and Android platform 36 instead of version 33 components.

Changes

Android SDK update

Layer / File(s) Summary
SDK component installation
Dockerfile
Updates the sdkmanager command to install build-tools;36.0.2 and platforms;android-36.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

I’m a rabbit hopping by,
New Android tools now reach the sky.
Thirty-six is in the box,
Fresh platform, sturdy locks.
Build and bounce—what a delight!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the Android SDK version upgrade in the Dockerfile.
Description check ✅ Passed The description is related to the Android build-tools upgrade and future Google Play deployment.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch android-build-tools-api-36

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

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@Dockerfile`:
- Line 18: Update the sdkmanager package request in the Dockerfile to use the
valid Build Tools identifier build-tools;36.0.0 while retaining
platforms;android-36. If the current command-line-tools archive cannot provide
that package, replace it with a newer commandlinetools-linux archive that does.
- Line 18: Update the Android command-line tools archive pin in the Dockerfile
download step to the current commandlinetools-linux *_latest.zip archive instead
of the hardcoded 7583922 version. Verify the resulting installation exposes
cmdline-tools/latest/bin/sdkmanager and that its --list output supports
installing build-tools;36.0.2 and platforms;android-36.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 82275284-733d-4ce6-91c8-0e6e2eb3dac3

📥 Commits

Reviewing files that changed from the base of the PR and between 336774a and 8425466.

📒 Files selected for processing (1)
  • Dockerfile

Comment thread Dockerfile Outdated
@BenjaminAmos

Copy link
Copy Markdown
Contributor Author

This is needed for MovingBlocks/DestSolAndroid@5babba4, so I am merging this now.

@BenjaminAmos
BenjaminAmos merged commit b27157f into main Jul 30, 2026
2 checks passed
@BenjaminAmos
BenjaminAmos deleted the android-build-tools-api-36 branch July 30, 2026 17:52
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.

1 participant