Hi, I suspect it was a weird local configuration issue that haunts me every now and then, but a restart and a full cache wipe resolved it again. I've proceeded with the 3.2.2 rc1 release and successfully completed almost all steps.
However, I encountered a Failed: Signature Validation error during the Maven publish process. Specifically, the signature is missing: ratis-bom-3.2.2.pom.asc does not exist. I’ve submitted a new PR[1] to address this, and I expect to start the RC2 release once it’s merged. [1] https://github.com/apache/ratis/pull/1374 Best --------------- Xinyu Tan On 2026/03/10 18:16:52 Attila Doroszlai wrote: > > 1. Delete ~/.m2/repository/org/apache/ratis > > 2. Run make_rc.sh > > > > Problem: > > The script fails with: ratis-bom not updated by `mvn versions:set` > > I have tried the above steps without any problem. > > export RATISVERSION=3.2.2 > export RC="-rc0" > export CODESIGNINGKEY=... > dev-support/make_rc.sh 1-prepare-src > > The same is tested by dev-support/checks/release.sh in CI ("release" check). > > Running "mvn versions:set -DprocessAllModules -DnewVersion=3.2.2" > instead of make_rc.sh also works for me. ratis-bom/pom.xml is > modified as expected. > > BTW, make_rc.sh uses Maven repo from $MVN_REPO_DIR, or > ../ratis.repository if the variable is not set. Please check if you > have this variable set, and if so, what is its value. > > -Attila >
