After prepare-release is invoked manually with a version, a tag and a commit that updates the version is pushed by the prepare-release.
deploy-release is run afterwards because it runs when a tag is pushed. This workflow will actually deploy the release to remote mvn repository. This workflow can also be run manually. After this runs, it'll create a github release as a draft with the release artifacts (sources jar and actual release jar). Then we'll update the changelog and release it.
The release process of hazelcast-wm will be described in a confluence page and reviewed by Nish. (wip)
Other changes:
maven-javadoc-plugin's javaApiLinks properties are removed because the link was being redirected to java 22 page, and also java 1.6/1.7 is unsupported now
@kwart @hasancelik @frant-hartm @nishaatr Hi gentlemen, didn't know who to add, so I added all of you. Feel free to suggest who should review this and others can remove themselves from the reviewer list.
Inspired by https://github.com/hazelcast/quarkus-hazelcast-client/tree/master/.github/workflows, this PR adds the workflows needed for semi-automated release workflow:
The release process of hazelcast-wm will be described in a confluence page and reviewed by Nish. (wip)
Other changes: