Hi Emond, The release was published to maven central before the announcement, shortly after the PMC votes were received. There are many steps to an announcement that need to be done and not all have been done yet. This is all in compliance with the ASF recommended release process.
Furthermore, the dates in maven central are the initial release staging dates, as opposed to publishing dates, which were about a week ago. I hope that the community appreciates a quicker release rather than waiting for all announcements to be completed. There is nothing wrong with the release and how it happened. If you have any doubts, all keys and SHA files are published and available to verify the release. > On Jun 25, 2026, at 1:27 PM, Emond Papegaaij <[email protected]> > wrote: > > Hi, > > I've got the feeling something went wrong with this release. We ran > our update tooling (based on the versions-maven-plugin) this morning, > way before you promoted the artifacts, and already picked up this > release. Are you sure this release wasn't promoted earlier? > Unfortunately, I don't have logging from our local artifactory to see > if it didn't pick up these files from some other repo, but at the > moment they are only cached on the maven central remote. You might > want to review your publishing steps. > > Best regards, > Emond > > Op do 25 jun 2026 om 19:43 schreef <[email protected]>: >> >> Hi, >> >> This vote passed with the following result: >> >> +1 (binding): Lenny Primak, Benjamin Marwell, François Papon, JB Onofré >> >> +1 (non-binding): Andreas Reichel >> >> I'm promoting the artifacts on Central and dist.apache.org, I will then >> announce the release. >> >> Thanks all for your vote! >> >> Lenny >>
