Howdy, respin #1 changes the staging repository, as my local repository contained some rogue Maven binaries (as revealed by SBOM), nothing changes ONLY the SBOM, release redone with `mvn deploy -P apache-release` AFTER nuking local repository.
We solved 6 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317521&version=12354997 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MGPG/issues Staging repo: https://repository.apache.org/content/repositories/maven-2204 Source release checksum SHA512: d03929bc679a755440605890c398bb146a0fd62ad52c81fc1204e5f908302fb0f98ad92cac181dda5767e97f31a0879459271ae67908ed789ff51cd76231a236 Staging site: https://maven.apache.org/plugins-archives/maven-gpg-plugin-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
