Are the compose releases somehow tagged in git? I'...
# compose
v
Are the compose releases somehow tagged in git? I'm trying to find a commit that has broken something between versions but it's not very handy to try to just operate on commit hashes
j
Which compose release you refer to?
There is a bunch of compose libraries, like compiler, compose multiplatform, foundation etc.
s
Not really, there are release branches we use for stable, but that's about it.
j
You can always check this one for latest BOM somewhat helpful, but depends which versions you using and which libs: https://developer.android.com/jetpack/compose/bom/bom-mapping
So yes sure you can get commits, but not easy collectable like GIthub release page collecting all compose libs.
v
I mean all the releases, the question was maybe more about the whole release process of androidx
v
I mean the use case I have is that I know that something breaks between 1.6.0 and 1.7.0-alpha01 and I'm too lazy to go through all commits one to figure out what causes it, so I'm probably just going to bisect through the commits and find the one that breaks
so I was wondering if there's any kind of tags in the git repo itself I could use to start easily, but I can look up the latest commit hashes in both releases' release notes and go with that
j
Not sure, havent found a nice page listing the git tags, not even sure GOogles AOSP using that to be honest. At least not regular git tags we are used to 😛
v
yeah Andrei just replied that there aren't any tags in the repo itself
I'll just use this thread as a memo if I forget: • 4c61c4d68d2bf0ccc61e316bc2a03754bb6979cf for 1.6.0 • 2b3fea6e026942389e9db59a4d68f2bb32c94e8f for 1.7.0-alpha01
s
Note that you cannot really compare alpha vs stable, they are in different branches
Alphas are cut from androidx-main, while releases are androidx-main of latest alpha + cherry picked fixes
👍🏼 1
v
It's ok, I can probably just look at starting from their common ancestor or take a look at their differences in only specific files
Found the commit, seems like there's some view <-> compose focus interop changes that are only implemented halfway through
🎉 1