IssueTracker

The script will re-apply the changes from the version change, but it should be a no-op a this point.

What does this mean? What do you believe should happen and what actually happened?

If you increment a version in build.gradle, then run fetch_all.py, then undo your change to build.gradle, then run fetch_all.py, it will not notice that you've undone your change to build.gradle.

Which package did you change? I don't believe the issue is that use stale pom files because that is not possible (we manually look it up ourselves and we don't cache them). The situation is probably more complicated than that. It is possible that it doesn't happen with all packages. Right now the only thing that I can think of that might be stale is the bill of materials in androidx which would probably mean only packages that androidx depends on transitively would have this problem.

I'll re-open if I can come up with a good repro.