When running mvn release:clean release:prepare for the new release/tag there is pushed new tag and GH action like (https://github.com/xtf-cz/xtf/actions/runs/17939682163) is triggred. This is redundant as the same thing happened on master branch and fails
What happens for mvn release:prepare is that:
- Updates the POM to a release version x.y and pushes this commit to master. At this point, master is at x.y (no -SNAPSHOT) and GH action with deploying the artificact to Nexus is triggered.
- A Git tag x.y is also created and pushed. Now the deploy is triggered again but fails as it was already deployed under the same version. Deploy for new tag is redundant.
- Immediately after tagging, it bumps the POM to the next snapshot version and pushes this commit to main/master. This updates/adds the new snapshot version which is ok.