ah so! under the fix I still seem to be running into the same issue if I have more than just the

<https://repo.osgeo.org/repository/release>

repo listed in our coursier config. seems like the "coursier eagerly choosing a bad pom from repo1.maven.org" problem persists if that repo is specified in the pants config