On Thu, Jan 16, 2025 at 2:13 PM PJ Fanning <fannin...@apache.org> wrote:
> > https://dist.apache.org/repos/dist/dev/pekko/PERSISTENCE-CASSANDRA-1.1.0-RC1/ > https://github.com/apache/pekko-persistence-cassandra/tree/v1.1.0-RC1 > Git commit ID: 2b91a5269106c238441c37b9a9e3e5950ba804b7 > > https://repository.apache.org/content/groups/staging/org/apache/pekko/ > > [x] Download links are valid. > [x] Checksums and signatures. > [x] LICENSE/NOTICE files exist > [x] No unexpected binary files > [x] All source files have ASF headers > [x] Can compile from source > [ ] Can verify the binary build > > > https://github.com/apache/pekko-site/wiki/Pekko-Release-Process#verifying-the-binary-build > The 'main' artifacts all reproduce, however the 'cassandra-launcher' artifacts do not: Judging from the META-INF/MANIFEST.MF, it seems the staged jar does not contain a freshly-built cassandra-bundler.jar, but a 1.1.0-M0+73-9c76067f+20240712-1357-SNAPSHOT one. Filed https://github.com/apache/pekko-persistence-cassandra/issues/259 . I also see the timestamp cassandra-bundle.jar in the launcher jar may be inconsistent, but let's verify that with a freshly-built cassandra-bundle.jar I have not tested the artifacts in any project This is my +1 for the release. For the binaries, let's make sure we rebuild cassandra-bundler.jar when we build the non-RC1 artifacts. -- Arnout Engelen ASF Security Response Apache Pekko PMC member, ASF Member NixOS Committer Independent Open Source consultant
