Automatization of release process

[graben]

The new release process doing with GitHub actions still need further automatization to do proper:

1. Switch version from SNAPSHOT to release version before upload to maven central
2. Switch to next SNAPSHOT version and commit changes to main branch

[graben]

FYI @aureamunoz

[cmoulliard]

Scenario to implement could be defined as such

current_version=$(mvn help:evaluate -Dexpression=project.version -q -DforceStdout)

release_version=${current_version%-SNAPSHOT}

IFS='.' read -r major minor patch <<<"${release_version}"
next_patch=$((patch + 1))
next_snapshot_version="${major}.${minor}.${next_patch}-SNAPSHOT"

echo "-------------------------------------"
echo "Current version: $current_version"
echo "Release version: $release_version"
echo "Next snapshot: $next_snapshot_version"

echo "-------------------------------------"
echo "Change the version of the pom to: $release_version"
mvn -q versions:set -DnewVersion=$release_version
echo "-------------------------------------"

echo "-------------------------------------"
echo "git tag $release_version
echo "git push"
echo "git release ..."
echo "mvn deploy ..."
echo "-------------------------------------"
sleep 5

# End of the process, bump the snapshot to the new version
echo "-------------------------------------"
echo "Bump the pom version ..."
mvn -q versions:set -DnewVersion=$next_snapshot_version
echo "git commit pom file updated"
echo "-------------------------------------"

[graben]

Hi @cmoulliard what about the "broken" releases already pushed to central? Isn't there a way to do a step to first push to a staging repo?

[cmoulliard]

Hi @cmoulliard what about the "broken" releases already pushed to central?

Hi. Sorry for the inconvenience as we had many issues end of last week to release on sonatype using the new process and renewed key not (yet) available publicly. Unfortunately we cannot delete what it has been pushed on maven central: https://central.sonatype.org/faq/can-i-change-a-component/#question

[graben]

Okay, I understand what's on maven central is frozen. That's why I was asking for something like a staging repo. That would help in those cases 🙂

[cmoulliard]

We have enabled snapshot on sonatype too. So that will be supported next time

The issue we faced is that when you release a snapshot on sonatype, then the sever don't verify the signature of the files generated from the private key (from our github job) and by example it was not possible to verify/validate the new process and key

[graben]

What I mean is set autoPublish to false and only waitUntil validated. This should solve the gpg issue with snapshots but do not publish until some verification and manual interaction. Could be better to have a release approval.

[graben]

Hi @aureamunoz, @cmoulliard, any further progress planned for this?

[aureamunoz]

Hi @graben! Not really, I'm back and I will dig on this next week. I'll let you know ;-)

[graben]

Hi @aureamunoz , I think it's a good time to release 3.4.3 as is and if everything is fine to close this issue. What do you think?

[aureamunoz]

Hi, Ok but it would be the 3.4.2, wouldn't it?

[graben]

Hi @aureamunoz , no it's 3.4.3 because 3.4.2.2 is the actual latest in maven-central and snapshot is set to 3.4.3. There were "broken" releases published, you remember?