8000 Add sentry-android-distribution module to release configuration by runningcode · Pull Request #4791 · getsentry/sentry-java · GitHub
[go: up one dir, main page]

Skip to content

Conversation

runningcode
Copy link
Contributor
@runningcode runningcode commented Oct 8, 2025

Summary

  • Add README.md to sentry-android-distribution module
  • Add module to main README.md packages table
  • Add module to .craft.yml sdks section
  • Remove module from publishing exclusion list in build.gradle.kts

This ensures the sentry-android-distribution module follows all requirements from .cursor/rules/new_module.mdc and will be properly published to Maven Central.

Solves EME-399

🤖 Generated with Claude Code

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Copy link
Contributor
github-actions bot commented Oct 8, 2025
Fails
🚫 Please consider adding a changelog entry for the next release.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

- Add sentry-android-distribution module to release configuration ([#4791](https://github.com/getsentry/sentry-java/pull/4791))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description or adding a skip-changelog label.

Generated by 🚫 dangerJS against 1fa618d

}

if (!this.name.contains("sample") && !this.name.contains("integration-tests") && this.name != "sentry-system-test-support" && this.name != "sentry-test-support" && this.name != "sentry-android-distribution") {
if (!this.name.contains("sample") && !this.name.contains("integration-tests") && this.name != "sentry-system-test-support" && this.name != "sentry-test-support") {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Potential bug: Incomplete distribution module will crash when used
  • Description: Publishing the sentry-android-distribution module exposes an incomplete implementation that throws a NotImplementedError when the checkForUpdateBlocking method is called, which will cause a crash for users.

  • Suggested fix: Complete the implementation of the checkForUpdateBlocking method in DistributionIntegration.kt to handle update checks gracefully instead of throwing a NotImplementedError. Alternatively, if the module is not ready for public use, revert the change that publishes it to Maven Central.
    severity: 3.0, confidence: 5.0

Did we get this right? 👍 / 👎 to inform future reviews.

maven:io.sentry:sentry-apache-http-client-5:
maven:io.sentry:sentry-android:
maven:io.sentry:sentry-android-core:
maven:io.sentry:sentry-android-distribution:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think for the first time it has to be manually added as described here: https://github.com/getsentry/sentry-release-registry#adding-new-sdks

After that we can merge the PR and it will be automatically published to the registry for future releases

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh. I was able to make a release already here: https://repo1.maven.org/maven2/io/sentry/sentry-android-distribution/8.24.0-alpha.1/
but I will do this!

Copy link
Member
@romtsn romtsn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, considering we add the distribution module to the release registry manually first :)

Copy link
Contributor
@chromy chromy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

0