Add Maven consumer link checks to release CI#873
Draft
ajpallares wants to merge 13 commits into
Draft
Conversation
Publish to Maven Local on Xcode 16.4, then link the sample app on Xcode 26.5 before the release hold gate. Co-authored-by: Cursor <cursoragent@cursor.com>
ajpallares
changed the title
Replace composeApp-based consumer checks with a minimal iOS-only app generated from the kmp.new template, and read Maven Local settings from gradle.properties during dependency resolution. Co-authored-by: Cursor <cursoragent@cursor.com>
Extend installationTestApp with a minimal Android target and gate releases on validate-android-consumer-link alongside the existing iOS check. Co-authored-by: Cursor <cursoragent@cursor.com>
Allows validating validate-publish and consumer link jobs on PR CI before keeping them release-only. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Prevents normal CI jobs from resolving unpublished Maven coordinates when configuration cache loads the full project graph. Co-authored-by: Cursor <cursoragent@cursor.com>
Consumer link checks remain on the release branch workflow only. Co-authored-by: Cursor <cursoragent@cursor.com>
ajpallares
commented
May 26, 2026
Comment on lines
+15
to
+17
| if (usePublishedMavenLocalArtifacts()) { | ||
| mavenLocal() | ||
| } |
Member
Author
There was a problem hiding this comment.
I'm not sure this is the best approach, since this could bite us locally. Do you think I should scope this only for the installation test app?
Always include installationTestApp with project deps by default, use explicit skipSigningForMavenLocal for validate-publish, and simplify the test app UI. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
… apiCheck. Gradle still configures kn-core when xcodebuild embeds the KMP framework, and installationTestApp is not part of the public API surface. Co-authored-by: Cursor <cursoragent@cursor.com>
Split Maven artifact resolution from Gradle project inclusion so consumer link jobs only configure installationTestApp and no longer need the purchases-ios submodule. Co-authored-by: Cursor <cursoragent@cursor.com>
This reverts commit 07aeda4.
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.
Checklist
purchases-android,purchases-iosand otherhybrids
Motivation
Follow-up to #872. Guards against #859 by validating Maven publish output and consumer linking before tagging a release.
Description
installationTestAppuses Maven Local in those jobs, project deps otherwise