Every push to develop/main triggers publish.yml's publish job, which runs publishToMavenCentral with a -SNAPSHOT version. It fails with:
Could not PUT '.../repository/maven-snapshots/dev/androidbroadcast/featured/featured-bom/1.0.0-SNAPSHOT/...pom'. Received status code 403 from server: Forbidden
Task :featured-bom:publishMavenPublicationToMavenCentralRepository FAILED
Root cause: SNAPSHOT deployment is not enabled for the dev.androidbroadcast namespace on the new Central Portal (central.sonatype.com). The real release (version 1.0.0, staging endpoint) is unaffected — only the SNAPSHOT branch builds fail.
Why this matters (priority): a Publish check that is red on every push trains maintainers to ignore it, so the next real publish failure will hide in the same red.
Fix options:
- (a) Gate
publishToMavenCentral off branch pushes — only run it for release tags (or only publish snapshots when explicitly enabled).
- (b) Enable snapshot deployment for the namespace on Central Portal and verify credentials/secrets.
Reference failed runs: 26701975087, 26694180198.
Every push to
develop/maintriggerspublish.yml'spublishjob, which runspublishToMavenCentralwith a-SNAPSHOTversion. It fails with:Root cause: SNAPSHOT deployment is not enabled for the
dev.androidbroadcastnamespace on the new Central Portal (central.sonatype.com). The real release (version1.0.0, staging endpoint) is unaffected — only the SNAPSHOT branch builds fail.Why this matters (priority): a Publish check that is red on every push trains maintainers to ignore it, so the next real publish failure will hide in the same red.
Fix options:
publishToMavenCentraloff branch pushes — only run it for release tags (or only publish snapshots when explicitly enabled).Reference failed runs: 26701975087, 26694180198.