Trying out the new compose BOM and I have a questi...

# compose

[Stylianos Gakis]

Trying out the new compose BOM and I have a question.
When a BOM is for say <5 libraries, it’s kinda easy to go through the release notes and check while updating if there’s anything to update with the new version. Compose BOM has 30 artifacts under itself though, meaning that when I am bumping it I can’t be sure I am taking care of everything I would if I did the bumps one by one.
And I am not talking about breaking changes in the code, I understand that the version upgrades are backwards compatible for the most part, but it’s also for stuff like when a library upgrades, sometimes they may introduce a new API which I see in the change log and go ahead and learn about it and use it immediatelly. This is not going to be happening with the BOM.
So a question, is there anywhere where for a specific BOM update I can also see a huge list of all the change logs for the versions that got updated?
A list of all the changelists that look like this; Example of compose material 1.3

Version 1.3.0 October 24, 2022

Important changes since 1.2.0

Behavior breaking change
Maximum supported elevation in dialogs and popups has been reduced to 8dp.

API Changes
Add a Pull-To-Refresh component to Compose (I29168).
Change parameter name from values to value in RangeSlider (I3b79a).

[Albert Chang]

I don't think there is.
It will be much more convenient if the versions in the mapping table link to the release notes pages for each library.

[Stylianos Gakis]

Oh yeah, that would work wonders too! Since I can then go and find the libs that I am in fact using and check them one by one.
But without any of these solutions, I’d say using the BOM becomes more of a burden than a positive 🤔
Maybe I’m wrong though, I’ll have to use it more to form a better opinion of how I like it or not.

[efemoney]

This is the way I browse compose releases https://developer.android.com/jetpack/androidx/versions/all-channel. You don’t have to look at 30 artifacts, just 6 links 🙂

[Stylianos Gakis]

Mm yeah, that looks like a nice centralized place to see the individual version updates. It however does not tell me which versions are in the bom files that I am bumping up to.
I guess I can simply check the date the new bom comes out and then come here and check the bumps that happened on that date. But that would also miss potentially important release notes if between 1 bom update, one of the underlying libraries has more than 1 release in this list 🤷‍♂️