Fix compose 1.10.2 build failure: add JetBrains Space dev repo to allprojects repositories#490
Merged
alorma merged 2 commits intodependabot/gradle/compose-1.10.2from Mar 10, 2026
Conversation
…se 1.10.2 build Co-authored-by: alorma <887462+alorma@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix build issue for pull request 487
Fix compose 1.10.2 build failure: add JetBrains Space dev repo to allprojects repositories
Mar 10, 2026
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
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.
Description
PR #487 (Dependabot bump of Compose 1.10.1 → 1.10.2) fails CI with
Cannot determine the version of Skiko for Compose '1.10.2'. The Compose Gradle plugin resolves the Skiko version by creating a detached configuration fororg.jetbrains.compose.ui:ui-graphics:<version>and inspecting its transitive deps — but this only works if the artifact is resolvable from project-level repositories.Root cause: Gradle's default
PREFER_PROJECTmode causesallprojects { repositories { ... } }inbuild.gradle.ktsto silently overridedependencyResolutionManagement.repositoriesinsettings.gradle.kts. The JetBrains Space dev repo was only in settings — meaning it was never actually used for dependency resolution. Compose 1.10.2 was freshly published (one day before CI ran) and not yet propagated to Maven Central, so the detached configuration couldn't findui-graphics:1.10.2.Related Issue
Type of Change
Changes Made
maven("https://maven.pkg.jetbrains.space/public/p/compose/dev")toallprojects { repositories }inbuild.gradle.kts, making it consistent with the already-correctdependencyResolutionManagement.repositoriesinsettings.gradle.ktsallprojects { repositories { google() mavenCentral() + maven("https://maven.pkg.jetbrains.space/public/p/compose/dev") } }Platforms Tested
Screenshots / Videos
Testing
Manual Testing
Automated Testing
Checklist
Additional Notes
This was a latent misconfiguration —
dependencyResolutionManagement.repositoriesinsettings.gradle.ktshad the JetBrains Space repo but it was never effective becauseallprojectsrepo declarations take precedence. Compose 1.10.1 happened to already be on Maven Central when CI ran; 1.10.2 was not yet propagated, exposing the bug.Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
https://api.github.com/repos/JetBrains/compose-multiplatform/releases/usr/bin/curl curl -s REDACTED(http block)maven.pkg.jetbrains.space/usr/bin/curl curl -s REDACTED(dns block)/home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.