Hi Tomas

in a recent update, the PushTagReleaseWorker and TagVersionReleaseWorker release workers are now always included by default in the release process.

In our company, we have a custom release process which requires us to create custom release workers, two of them that fill the role of the default release workers, amongst other things.
It was working well prior the update, but now the two default release worker try to do their thing, which causes some conflict (one of our release workers takes care of creating the local tag, which the TagVersionReleaseWorker also tries to do).

What would be the most elegant way to disable this behavior?

Thanks for your help.