Yes, I can confirm this timeline. I’m glad that your upgrade went fine and thank you for the kind words.
Anything you can do to support Shiro would be appreciated. > On Jun 25, 2026, at 2:29 PM, Emond Papegaaij <[email protected]> > wrote: > > Hi Lenny, > > The timestamps on the artifacts are 2026-06-20 20:14. This probably is > the moment of initial staging. However, the timestamp of the metadata > file is 2026-06-24 18:13 (yesterday). These files are regenerated when > the directory contents change, so they usually reflect the moment a > new version is added. So, if you promoted these files yesterday > because voting passed, then all is fine. I just wanted to give you an > heads up because I noticed a discrepancy between the moment of this > mail and the moment we picked up the release. > > Btw, congrats on the 3.0.0 release of this project! Over 15 years and > still going strong! We've already migrated our project to 3.0.0, and > the only minor issue we hit was a long forgotten call to ThreadContext > that no longer worked due to the switch to ScopedValue. > > Best regards, > Emond > > Op do 25 jun 2026 om 20:52 schreef Lenny Primak <[email protected]>: >> >> 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 >>>> >>
