Skip to content

fix(auto-install): Use BOM version for Sentry installs#1349

Open
adinauer wants to merge 2 commits into
mainfrom
side-quest/sagp-bom-version-use-skill-create
Open

fix(auto-install): Use BOM version for Sentry installs#1349
adinauer wants to merge 2 commits into
mainfrom
side-quest/sagp-bom-version-use-skill-create

Conversation

@adinauer

@adinauer adinauer commented Jul 1, 2026

Copy link
Copy Markdown
Member

Use the Sentry BOM version as the source of truth for auto-installed SDK dependencies.

Previously SAGP treated sentry-bom like a concrete SDK dependency when choosing whether to install the core SDK. That avoided adding sentry-android, but it also meant BOM-only projects could not use the BOM version for the dependencies SAGP installs.

This separates version detection from SDK presence detection. Concrete Sentry SDK dependencies still prevent SAGP from adding the core SDK again, while sentry-bom and sentry-opentelemetry-bom provide the version used for auto-installed dependencies.

adinauer and others added 2 commits July 1, 2026 16:27
Detect Sentry BOM dependencies separately from concrete Sentry SDK dependencies so auto-install can use the BOM-selected SDK version without treating a BOM as the installed SDK.

This keeps integration installs aligned with sentry-bom and sentry-opentelemetry-bom declarations while still adding the core SDK when only a BOM is present.

Co-Authored-By: Claude <noreply@anthropic.com>
Document the auto-install fix now that the pull request number is available.

Co-Authored-By: Claude <noreply@anthropic.com>

@runningcode runningcode left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Great improvement!

@linear-code

linear-code Bot commented Jul 10, 2026

Copy link
Copy Markdown

GRADLE-112

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