fix(publish): don't re-publish omsdk-android on every release - #11
Merged
Conversation
…shOmsdk vanniktech bundles every module in one `publishToMavenCentral` invocation into a single Central Portal deployment. Since omsdk-android's coordinate (so.kontext.iab:omsdk-android:1.6.4) is immutable on Maven Central and its version is independent of KontextKit's semver, every normal release tried to re-upload it — the existing coordinate fails component validation and takes down the whole deployment (this blocked the 0.0.7 release). Disable the omsdk-android Central-publish tasks unless `-PpublishOmsdk=true`, so a normal release deployment carries only kontext-kit-android. Pass the flag only when actually bumping the bundled IAB AAR. Verified: `./gradlew :omsdk-android:publishToMavenCentral` skips all of its MavenCentral tasks (incl. the staging task) by default; the escape-hatch flag re-enables them. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
0.0.7Maven Central publish failed validation:./gradlew publishToMavenCentralbundles every module in the invocation into a single Central Portal deployment.so.kontext.iab:omsdk-android:1.6.4was already published with0.0.6, and Maven Central coordinates are immutable — so re-uploading it fails component validation and takes down the whole deployment. Result:kontext-kit-android:0.0.7never published.The OMID AAR version is independent of KontextKit's semver, so it should be published once per AAR bump, not on every KontextKit release.
Fix
Disable
:omsdk-android's Maven Central tasks unless-PpublishOmsdk=true. Normal releases (./gradlew publishToMavenCentral) now publish onlykontext-kit-android. When the bundled IAB AAR is actually updated, publish it explicitly with-PpublishOmsdk=true.Verified:
./gradlew :omsdk-android:publishToMavenCentral(default) skips all omsdk MavenCentral tasks — including the staging task that writes into the deployment bundle — and succeeds with no network call.Release note
No consumer-facing change.
kontext-kit-android:0.0.7content is unchanged; this only stops the redundantomsdk-androidre-upload. Reusing the0.0.7version (it never published).🤖 Generated with Claude Code