You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is like cl/782079419 but for our other projects. (Specifically, I covered Guava and all the projects with `pom.xml` files that I'm used to updating for a new Guava release. I haven't tried to find any projects we run _without_ Guava dependencies (if any) or any that use Bazel instead of Maven.)
As in the previous CL, I have updated the GitHub CI repository secrets as described in https://central.sonatype.org/publish/generate-portal-token/, **but** I have done so only for projects where I have deployment permission (specifically, Compile-Testing, Guava, and Truth). The others (Auto and Caliper) will need to be updated by someone who has publication permission for those projects. (Actually, it looks like Caliper doesn't actually deploy CI snapshots, even though it seems to have Sonatype credentials saved in GitHub. Hmm.) And CI snapshot releases aside, anyone who wants to deploy a "true" release will need to enter a token into `~/.m2/settings.xml`, again as discussed in cl/782079419.
RELNOTES=n/a
PiperOrigin-RevId: 785997601
0 commit comments