elharo opened a new pull request, #105: URL: https://github.com/apache/maven-changes-plugin/pull/105
I think I finally understand why the dependency analyzer has such a tizzy about hamcrest dependencies. 3.0 and 1.3 seem to have put different classes in different artifacts, and JUnit 4 depends on Hamcrest 1.3. As long as we match the Hamcrest version to the JUnit version everything's hunky dory. However if we let dependabot or anything else upgrade to Hamcrest 3, things go haywire. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org