docs: update README for v2.6.0

[Manabu-GT]

Summary

• Bumped install snippets from 2.5.0 to 2.6.0 across Quick Start, Version Catalog, Kotlin DSL, the OkHttp / Timber / shake-trigger extensions, and the releaseWithOverlay example.

Test plan

• Verify rendered README on GitHub shows 2.6.0 in every code snippet
• Confirm no stale 2.5.0 references remain (grep -n "2\.5\.0" README.md)

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

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

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 550b5462-36d5-4306-a0c0-d7dc27b28c34

📥 Commits

Reviewing files that changed from the base of the PR and between 203ea3b and 71be140.

📒 Files selected for processing (1)

• README.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/readme-v2.6.0

---

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

[claude]

Claude finished @Manabu-GT's task in 1m 5s —— View job

---

Claude Code Review

• Read the PR diff
• Inspect README to verify no stale 2.5.0 references remain
• Cross-check version against project source of truth (CHANGELOG.md / gradle.properties)
• Post review feedback

---

Summary

LGTM — this is a clean, mechanical docs-only version bump. Exactly what's described on the tin.

Verification

Check	Result
All 10 2.5.0 → 2.6.0 replacements present	✅ Verified via grep (matches PR's +10/-10)
No stale 2.5.0 left in README.md	✅ grep -n "2\.5\.0" README.md returns nothing
Stale 2.5.0 elsewhere in repo	✅ Only CHANGELOG.md:10 (correct — historical entry)
CHANGELOG.md has a 2.6.0 section	✅ ## Version 2.6.0 *(2026-05-18)* at line 3
Locations updated match the install-snippet inventory in the PR body	✅ Quick Start (L31), Version Catalog (L76), Kotlin DSL (L102), Shake (L157–158), OkHttp (L210–211), Timber (L242–243), releaseWithOverlay (L367)

Findings

• Code quality / correctness: Nothing to flag — pure string substitution, every site is a coordinate inside a code fence.
• Bugs / security / performance: Not applicable (docs only).
• Consistency: CHANGELOG, README, and the parent PR [docs][refactor] update README/CHANGELOG for maxLogcatEntries + refactor LogcatDataSource #249 (which landed the actual feature docs for [feat] add maxLogcatEntries new config param #247 / [feat] add a thermal status row to the debug overlay panel #248) line up — this PR's narrowed scope is the right call.

Non-blocking FYI (not part of this PR's scope)

• gradle.properties:34 still reads VERSION_NAME=2.0.0-SNAPSHOT. This is the in-tree working version and is presumably overridden at publish time, but worth a glance if the release flow expects it to track the published version. Definitely not something to fix in a README-only PR.

Ready to merge from a review standpoint.
· Branch: docs/readme-v2.6.0

[github-actions]

Qodana for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions