Sonatype and Javadoc snapshots broken

[cpovirk]

Sonatype snapshots were fine on Mar 17 but not Mar 20:

Error: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.1.2:deploy (default-deploy) on project jimfs-parent: Failed to deploy artifacts: Could not transfer artifact com.google.jimfs:jimfs-parent:pom:HEAD-20250320.173440-214 from/to sonatype-nexus-snapshots (https://oss.sonatype.org/content/repositories/snapshots/): status code: 401, reason phrase: Content access is protected by token (401) -> [Help 1]

I think we've seen some flakiness with that before, though, so I wouldn't worry too much yet.

Javadoc was fine on Feb 24 but not on Mar 5:

remote: Permission to google/jimfs.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/google/jimfs.git/': The requested URL returned error: 403

Compare issues like google/auto#1832 and google/auto#1900.

[cpovirk]

Apparently snapshots were fine again on March 21, and they have probably been fine since.

[cpovirk]

Sorry, to be more specific: That's just Sonatype snapshots. Javadoc is still broken.

[cpovirk]

(And then Sonatype snapshots broke again from the OSSRH->Central migration :))

[cpovirk]

Sonatype snapshots are fixed again. Javadoc snapshots remain broken.