Bump android-ci pin so Sonar analyses develop - #1843
Conversation
Picks up the Sonar step fix from stream-build-conventions-android#78. Until it lands, SonarCloud's develop baseline for this repo is frozen at 2025-12-19 and every PR gate measures new code against it.
PR checklist ✅All required conditions are satisfied:
🎉 Great job! This PR is ready for review. |
SDK Size Comparison 📏
|
|
Understand this PR’s impact Explore downstream dependencies and potential security impact with Blast Radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. WalkthroughThe Android CI workflow now references a newer commit of the shared ChangesAndroid CI
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Bug fix Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. A rabbit hops through checks anew Comment |
stream-build-conventions-android#78 squash-merged as 68c8917. The previous pin was that PR's branch commit, which carried an earlier form of the Sonar condition and sits on a now-deleted branch.
|



Goal
Refs AND-1443
SonarCloud last analysed this repo's
developon 2025-12-19. The Sonar step in theshared workflow is gated on a
pull_requestfield that is empty on push, so it hasonly ever run on PRs and never refreshes the branch baseline. Every PR gate here
measures new code against that frozen baseline.
Implementation
Bump the
android-ci.ymlpin in.github/workflows/android.ymlto pick upGetStream/stream-build-conventions-android#78. No other pin touched.
Testing
actionlint .github/workflows/android.yml— clean.Draft until #78 merges. It is currently pinned to that PR's branch commit
(
2e7e495). The conventions repo squash-merges and cuts version tags — the previouspin
8b36d37disv0.14.0— so this must be re-pinned to the new release before itcan merge. Expect a large one-off issue count on the first clean
developanalysis;that is the backlog becoming visible, not a regression.
Summary by CodeRabbit