When you create a release branch via yarn create-release-branch -i, the commit that it creates is called "Update Release X.Y.Z". If you then create a pull request and merge that pull request, it will not result in initiating the release workflow, because "Update Release X.Y.Z" is not a valid title for a release. Many engineers have worked around this by retitling the PR upon creating it, but that is not ideal. The tool ought to name the commit "Release X.Y.Z" instead.
When you create a release branch via
yarn create-release-branch -i, the commit that it creates is called "Update Release X.Y.Z". If you then create a pull request and merge that pull request, it will not result in initiating the release workflow, because "Update Release X.Y.Z" is not a valid title for a release. Many engineers have worked around this by retitling the PR upon creating it, but that is not ideal. The tool ought to name the commit "Release X.Y.Z" instead.