Uh oh!
There was an error while loading. Please reload this page.
Publish explicit versions for BOM-managed Compose dependencies - #9
Merged
Conversation
Maven Central rejects a POM that declares a dependency without a version. The Compose BOM supplies those versions at resolution time, but a BOM does not travel in the published POM, so consumers who do not import the BOM themselves get an unresolvable dependency. Give the BOM-managed Compose artifacts an explicit version (`composeLibs`, 1.7.8 — what compose-bom 2025.02.00 resolves to) so the version reaches the POM. The BOM still governs resolution; this only fixes what is published. Release as 1.3.1: Maven Central versions cannot be replaced.
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 freeto 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.
Maven Central rejects a POM that declares a dependency without a version. The
Compose BOM supplies those versions at resolution time, but a BOM does not
travel in the published POM, so consumers who do not import the BOM themselves
get an unresolvable dependency.
Give the BOM-managed Compose artifacts an explicit version (
composeLibs,1.7.8 — what compose-bom 2025.02.00 resolves to) so the version reaches the POM.
The BOM still governs resolution; this only fixes what is published.
Release as 1.3.1: Maven Central versions cannot be replaced.