Skip to content
This repository was archived by the owner on Apr 26, 2026. It is now read-only.

chore(android): update compileSdk and targetSdk to API 35 (Android 15)#35

Merged
hyochan merged 2 commits into
mainfrom
improvement/update-android-sdk-35
Mar 25, 2026
Merged

chore(android): update compileSdk and targetSdk to API 35 (Android 15)#35
hyochan merged 2 commits into
mainfrom
improvement/update-android-sdk-35

Conversation

@hyochan

@hyochan hyochan commented Mar 25, 2026

Copy link
Copy Markdown
Owner

Summary

Updates Android SDK versions from API 34 to API 35 (Android 15) in the Gradle version catalog.

Changes

  • android-compileSdk: 34 → 35
  • compileSdk: 34 → 35
  • targetSdk: 34 → 35

Why

  • Android 15 (API 35) has been the stable release since October 2024
  • Targeting the latest stable API level ensures access to new APIs and keeps the library aligned with Google Play requirements
  • Google Play will eventually require targetSdk 35 for new app updates
  • minSdk is unchanged at 24 to maintain broad device compatibility

Summary by CodeRabbit

Chores

  • Updated Android SDK version targets to Android 35, ensuring compatibility with the latest platform and incorporating the latest security updates.

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the project's Android SDK versions to API 35 (Android 15). This change ensures the project remains compatible with the latest Android platform features and adheres to Google Play's evolving requirements for app submissions, while maintaining broad device compatibility by keeping minSdk at 24.

Highlights

  • Android SDK Update: Updated compileSdk and targetSdk to API 35 (Android 15) in the Gradle version catalog.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai

coderabbitai Bot commented Mar 25, 2026

Copy link
Copy Markdown
Contributor

Warning

Rate limit exceeded

@hyochan has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 14 minutes and 21 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ddeceb25-26dd-4b1b-96fa-3a2b7e60c224

📥 Commits

Reviewing files that changed from the base of the PR and between c85c292 and 59cad97.

📒 Files selected for processing (2)
  • example/composeApp/build.gradle.kts
  • gradle/libs.versions.toml
📝 Walkthrough

Walkthrough

Updated Android SDK version targets in gradle/libs.versions.toml by incrementing android-compileSdk, compileSdk, and targetSdk from version 34 to version 35 across the configuration file.

Changes

Cohort / File(s) Summary
Android SDK Version Bump
gradle/libs.versions.toml
Updated three SDK version constants from 34 to 35: android-compileSdk, compileSdk, and targetSdk.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

﹩ openiap

Poem

🐰 Hopping through versions with glee,
SDK thirty-five now we see,
Android updated, the targets align,
Compiled and ready, everything's fine! 🚀

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: updating Android SDK versions to API 35, with the PR addressing compileSdk and targetSdk changes across the codebase.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch improvement/update-android-sdk-35

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 and usage tips.

@gemini-code-assist gemini-code-assist 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.

Code Review

This pull request updates the Android SDK versions (android-compileSdk, compileSdk, and targetSdk) from 34 to 35 in gradle/libs.versions.toml. The review feedback highlights an opportunity to improve version management by noting that compileSdk and targetSdk are currently unused and redundant, suggesting consolidation and removal of these entries for better clarity and consistency.

Comment thread gradle/libs.versions.toml Outdated
- Remove unused `compileSdk`, `targetSdk`, and `minSdk` entries
- Add `android-targetSdk` to version catalog
- Refactor example app to reference version catalog instead of hardcoding

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@hyochan hyochan merged commit f8e4a95 into main Mar 25, 2026
4 checks passed
@hyochan hyochan deleted the improvement/update-android-sdk-35 branch March 25, 2026 08:07
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant