On Sat, Jan 11, 2025 at 1:28 PM PJ Fanning <fannin...@apache.org> wrote: > https://dist.apache.org/repos/dist/dev/pekko/CONNECTORS-1.1.0-RC1/ > https://github.com/apache/pekko-connectors/tree/v1.1.0-RC1 > Git commit ID: 63f1cefac096f21a93b8ae64a395d4c6bce43caa > [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 > [x] Can verify the binary build > > https://github.com/apache/pekko-site/wiki/Pekko-Release-Process#verifying-the-binary-build
All staged pom's info.apiURL fields (e.g. in https://repository.apache.org/content/groups/staging/org/apache/pekko/pekko-connectors-amqp_2.12/1.1.0-RC1/pekko-connectors-amqp_2.12-1.1.0-RC1.pom) point to https://pekko.apache.org/api/pekko-connectors/current/ while if I build locally it is https://pekko.apache.org/api/pekko-connectors/1.1.0-RC1/ . That would be good to fix but does not need to hold up the release. PJ: do you know what could've caused this or should we create an issue? All main jars for Scala 2.12 and 2.13 are binary reproducible. For Scala 3.3, I had to 'SBT_OPTS="-Xmx5g" sbt +reproducibleBuildsCheck' because 'sbt ++3.3 reproducibleBuildsCheck' failed to build. Here, pekko-connectors-google-fcm_3-1.1.0-RC1.jar, pekko-connectors-huawei-push-kit_3-1.1.0-RC1.jar and pekko-connectors-mqtt-streaming_3-1.1.0-RC1.jar didn't reproduce due to https://github.com/scala/scala3/issues/21154 which indeed should be fixed on 3.3.5 while we're on 3.3.4. All other jars reproduced successfully. I have not tested the release in any project. This is my +1 Kind regards, -- Arnout Engelen ASF Security Response Apache Pekko PMC member, ASF Member NixOS Committer Independent Open Source consultant --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org For additional commands, e-mail: dev-h...@pekko.apache.org
