Add Compose BOM changelog to Resources#424
Open
keymusicman wants to merge 2 commits into
Open
Conversation
keymusicman
changed the title
keymusicman
changed the title
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.
What is it?
compose-bom.com is an open-source, static community tool that diffs any two
Jetpack Compose BOM versions and aggregates the underlying library release notes.
Example: https://compose-bom.com/?from=2026.03.01&to=2026.05.00
Source: https://github.com/keymusicman/compose-bom-changelog
Why include it?
compose-bom.com fills a gap Google's official docs don't cover: there's no
changelog for the Compose BOM itself, so developers have to cross-reference each
library manually when evaluating an upgrade. This tool does that in one click.