ci(danger): Demote Android SDK version mismatch from fail to warn

[antonis]

📢 Type of change

• Bugfix
• New feature
• Enhancement
• Refactoring

📜 Description

Downgrade the Danger check in scripts/check-android-sdk-mismatch.js from fail() to warn() when the sentry-android version in packages/core/android/build.gradle differs from the version bundled by the pinned Sentry Android Gradle Plugin (AGP).

The message is also updated to reflect that the crash is conditional on AGP autoInstallation being enabled, and to point reviewers at the docs-based mitigation rather than treating the mismatch as a guaranteed crash.

💡 Motivation and Context

The check was originally added as a hard fail because an IllegalStateException: Sentry SDK has detected a mix of versions crash can occur at app startup when AGP's autoInstallation (default: true) pulls in a different sentry-android version than the one shipped by @sentry/react-native.

Since then, the docs have been updated to explicitly instruct React Native users to disable autoInstallation in their android/app/build.gradle:

• docs(react-native): Add warning about AGP autoInstallation on Android sentry-docs#17349 — adds warning alerts to the manual setup guide and v7→v8 migration page, plus a dedicated troubleshooting section for the IllegalStateException.

Per internal discussion, adding AGP to a React Native app is an explicit opt-in step, and users performing that step are expected to follow the setup guide — which now prominently instructs them to set autoInstallation.enabled = false. In that world, a version mismatch between our bundled sentry-android and the version AGP would auto-install is no longer a guaranteed crash: it only affects users who both opt into AGP and ignore the documented configuration.

Keeping the check as fail() couples RN SDK release cadence to gradle plugin release cadence (we couldn't bump sentry-android until a matching AGP release shipped), without providing meaningful additional protection over the docs. Demoting to warn() preserves reviewer visibility while unblocking dependency bumps.

💚 How did you test it?

• Manual review of the updated Danger rule; all other branches in the script already emit warn() with a ⚠️ icon, so the mismatch branch is now visually and behaviorally consistent with them.
• The check path is otherwise unchanged — same parsing, same upstream fetch, same comparison; only the severity and message content change.

📝 Checklist

• I added tests to verify changes
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled
• I updated the docs if needed.
• I updated the wizard if needed.
• All tests passing
• No breaking changes

🔮 Next steps

[github-actions]

Semver Impact of This PR

⚪ None (no version bump detected)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

• ci(danger): Demote Android SDK version mismatch from fail to warn by antonis in #6018

• chore(deps): update JavaScript SDK to v10.49.0 by github-actions in #6011
• ci: Integrate Warden for AI-powered PR code review by antonis in #6003
• chore(lint): Fixes lint issue on main by antonis in #6013
• feat(expo): Warn when prebuilt native projects are missing Sentry config by alwx in #5984

---

_{🤖 This preview updates automatically when you update the PR.}

[github-actions]

	Fails
🚫	Pull request is not ready for merge, please add the "ready-to-merge" label to the pull request

Generated by 🚫 dangerJS against 6fb08f7