Additionally, the git tag v2.6.0 doesn't seem to fully correspond to Error Prone 2.6.0. In particular, the
pom files at that tag list the version as HEAD-SNAPSHOT, while the Maven central artifacts do have 2.6.0 correctly set up in their pom files. Not sure if there are also Java code differences between the code at that tag and the published jars... is it possible the wrong commit was tagged?
Nothing urgent, since we can just stay on 2.5.1, but I'd love some clarity on whether the tag is correct before we upgrade, since we fork some of the Error Prone jars internally (but not others) :)