This splits the release workflow into two separate workflows.
The release-perform.yml is triggered when a tag is pushed or can also be invoked manually (for cases where central isn't behaving properly and a retry may be necessary).
Note that you can already retry failed steps in the existing release.yml workflow, however it will use the same SHAs for the reusable workflows, meaning that if the workflow has a bug and needs to change, you can't rely on the "Retry Failed Jobs".
This splits the release workflow into two separate workflows.
The
release-perform.ymlis triggered when a tag is pushed or can also be invoked manually (for cases where central isn't behaving properly and a retry may be necessary).Note that you can already retry failed steps in the existing release.yml workflow, however it will use the same SHAs for the reusable workflows, meaning that if the workflow has a bug and needs to change, you can't rely on the "Retry Failed Jobs".