The await-maven-artifact job and all its dependents should not depend on the actual release-task:
It is possible that the maven-publish succeeded, but something else was wrong with the workflow (e.g. the GH-release could not be created due to a workflow error).
In that case we'll need to update the workflow and retrigger the release while skipping the maven-central deployment.
This will only work if those follow up jobs don't directly depend on the release job, because otherwise they'll be skipped aswell.
The await-maven-artifact job and all its dependents should not depend on the actual release-task:
It is possible that the maven-publish succeeded, but something else was wrong with the workflow (e.g. the GH-release could not be created due to a workflow error).
In that case we'll need to update the workflow and retrigger the release while skipping the maven-central deployment. This will only work if those follow up jobs don't directly depend on the release job, because otherwise they'll be skipped aswell.