Open davidhwilliams opened 11 months ago
The reason is that adding releases to Github is manual work, and releasing to Maven Central automatic (one command line command), so making Github releases tends to be forgotten until someone asks for them. Happened with 2.5.0 and 2.5.1 as well https://github.com/wvengen/proguard-maven-plugin/issues/163
Based on Git blame for pom.xml
I think these commits are missing the tags:
2.5.3-SNAPSHOT
, so could have been later commit as well)2.6.0-SNAPSHOT
, so could have been later commit as well)
Missing versions 2.5.2, 2.5.3, and 2.6.0 from releases.
https://search.maven.org/artifact/com.github.wvengen/proguard-maven-plugin/2.6.0/maven-plugin lists this repo as the source code. Is there a reason the releases don't match up?