Home Original page

chore: update Android SDK tools to version 35 and adjust README for API levels 31-35 by fontsie · Pull Request #53 · beevelop/docker-android

Walkthrough

Updated Dockerfile to upgrade Android command-line tools and build-tools, refactored SDK installation (platforms and extras), added Gradle and package installs, and fixed ENV PATH syntax; README updated to reference Android 15 (API 31–35) and Java 17.0.12.

Changes

Cohort / File(s) Change Summary
Container build & Android SDK setup
Dockerfile		 Updated commandlinetools URL to 13114758, Android build-tools to 35.0.0; switched to ENV PATH=$PATH:...; replaced apt-get with apt --no-install-recommends and added unzip; added Gradle 8.12 installation and symlink; reworked SDK extraction and file moves; adjusted sdkmanager targets (removed 28–30, kept 31–33, added 34–35); revised extras/add-ons list; tightened cleanup steps.
Documentation
README.md		 Updated supported Android versions to Android 15 (API 31–35); bumped Java reference to 17.0.12; updated Gradle version to 8.12; minor whitespace cleanup.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant Docker as Docker Build
    participant Apt as Package Manager
    participant Files as FS (unpack/move)
    participant SDK as sdkmanager

    Dev->>Docker: docker build
    Docker->>Apt: apt update && apt install (wget, curl, unzip, maven, ant, gradle ...)
    Docker->>Docker: Download and unpack commandlinetools (13114758)
    Docker->>Files: reorganize cmdline-tools into cmdline-tools/latest
    Docker->>Docker: Install Gradle 8.12 and create symlink
    Docker->>SDK: sdkmanager --install platforms (31–33,34–35), build-tools 35.0.0, extras/add-ons
    Docker->>Docker: set ENV (ANDROID_SDK_ROOT, PATH=...)
    Docker-->>Dev: Built image with updated toolchain
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Poem

I nibbled through layers, found tools anew,
Pulled commandlinetools and Gradle too.
Leapfrogged build-tools to thirty-five,
Tidied PATH so builds can thrive.
Docs now sing of Android fifteen—hop, hop, woo! 🥕🐇

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

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

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.