Maven Central is more definitive than MvnRepository. I see 1.40 artifacts have correctly deployed to Central.
https://central.sonatype.com/artifact/org.apache.calcite/calcite-core/versions On Wed, May 28, 2025 at 8:53 AM Alessandro Solimando <[email protected]> wrote: > > Hello, > the release plugin failed with a 500 error for Nexus (most probably as I > tried and dry-run that altered the nexus id in the txt file), so I have > decided to continue manually the release process as suggested in the howto > [1], by following the instructions under this issue [2]. > > What I have checked so far that is fine: > 1) git: all seems in order (commit hash and tags are aligned with the VOTE) > - history: https://github.com/apache/calcite/commits/main/ > - release commit: > https://github.com/apache/calcite/commit/e2e77aaf172ce997b92a9e574b5fcf77a6dc297a > - release tag: https://github.com/apache/calcite/releases/tag/calcite-1.40.0 > 2) website: https://calcite.apache.org/docs/history.html#v1-40-0 > 3) release artifacts in Calcite website: > https://calcite.apache.org/downloads/#source-releases (tar and digest are > available and matching those of the VOTE email) > 4) Apache Nexus: > https://repository.apache.org/content/repositories/releases/org/apache/calcite/calcite-core/1.40.0/ > > What is missing or I am unsure of: > 1) https://mvnrepository.com/artifact/org.apache.calcite/calcite-core: > there is still not 1.40.0 (it might just be propagation time?) > 2) SVN Apache Archive: https://archive.apache.org/dist/calcite/ (1.40.0 is > missing) > > Can people familiar with the process double-check and suggest what to do > for the missing parts, please? > > I am holding back the announcement email until all points are clarified. > > Best regards, > Alessandro > > [1] https://calcite.apache.org/docs/howto.html#making-a-release-candidate > [2] https://github.com/vlsi/vlsi-release-plugins/issues/64
