Skip to content

ref(build): Move apply<MavenPublishPlugin>() outside afterEvaluate#5464

Merged
runningcode merged 1 commit into
mainfrom
no/ref/move-maven-publish-outside-after-evaluate
May 22, 2026
Merged

ref(build): Move apply<MavenPublishPlugin>() outside afterEvaluate#5464
runningcode merged 1 commit into
mainfrom
no/ref/move-maven-publish-outside-after-evaluate

Conversation

@runningcode
Copy link
Copy Markdown
Contributor

@runningcode runningcode commented May 22, 2026

📜 Description

Move apply<MavenPublishPlugin>() (Gradle's built-in maven-publish plugin) outside of the afterEvaluate block in the root build.gradle.kts.

💡 Motivation and Context

Applying plugins inside afterEvaluate is a Gradle anti-pattern that can cause ordering issues and makes the build harder to reason about. The maven-publish plugin can be applied eagerly alongside the other plugins in the same block.

💚 How did you test it?

  • ./gradlew spotlessApply apiDump passes
  • ./gradlew projects configures successfully

📝 Checklist

  • I added GH Issue ID & Linear ID
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • No breaking change or entry added to the changelog.
  • No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

None.

#skip-changelog

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@sentry
Copy link
Copy Markdown

sentry Bot commented May 22, 2026

📲 Install Builds

Android

🔗 App Name App ID Version Configuration
SDK Size io.sentry.tests.size 8.42.0 (1) release

⚙️ sentry-android Build Distribution Settings

@runningcode runningcode marked this pull request as ready for review May 22, 2026 12:56
@runningcode runningcode merged commit 44472da into main May 22, 2026
72 checks passed
@runningcode runningcode deleted the no/ref/move-maven-publish-outside-after-evaluate branch May 22, 2026 13:54
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.

2 participants