Automatic updating of conformance test reports when the test suite changes is broken

[netdpb]

See example run.

FAILURE: Build failed with an exception.

* Where:
Build file '/home/runner/work/jspecify-reference-checker/jspecify-reference-checker/reference-checker/build.gradle' line: 157

* What went wrong:
A problem occurred configuring root project 'jspecify-reference-checker'.
> Could not create task ':conformanceTests'.
   > Could not create task ':unzipConformanceTestSuite'.
      > Could not resolve all files for configuration ':conformanceTestSuite'.
         > Could not resolve org.jspecify.conformance:conformance-tests:0.0.0-SNAPSHOT.
           Required by:
               root project :
            > Could not resolve org.jspecify.conformance:conformance-tests:0.0.0-SNAPSHOT.
               > Unable to load Maven meta-data from https://ossrh-staging-api.central.sonatype.com/service/local/staging/deploy/maven2/org/jspecify/conformance/conformance-tests/0.0.0-SNAPSHOT/maven-metadata.xml.
                  > Could not GET 'https://ossrh-staging-api.central.sonatype.com/service/local/staging/deploy/maven2/org/jspecify/conformance/conformance-tests/0.0.0-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized

[netdpb]

@cpovirk could this have something to do with changes to how we publish to Maven?

[cpovirk]

Hmm, that could well be.

I think that ossrh-staging-api.central.sonatype.com is https://central.sonatype.org/publish/publish-portal-ossrh-staging-api/. I've been referring to it as a "legacy shim," which aims to let people publish their projects much like they did before the OSSRH->Central transition instead of making the full transition. I wonder if its "partial reimplementation" supports writes but not reads? Maybe there's a way to specify a different URL for reads? (My other guess would have been that we're using credentials from the old system and not the new one. But I think you already switch us over a month or so ago.)