Using merge back requires a removal of a security feature
Pushing to release before merging the change log makes rolling back awkward if there is an issue found in the changelog PR.
What was the solution? (How)
release:bump no longer merges, it only create the PR for the change log. release:publish now runs when a push is made to mainline with a modification to CHANGELOG.md. If the commit was made by ci, then it will merge mainline to release and follow with the release and publish jobs.
What was the problem/requirement? (What/Why)
What was the solution? (How)
release:bump no longer merges, it only create the PR for the change log. release:publish now runs when a push is made to mainline with a modification to CHANGELOG.md. If the commit was made by ci, then it will merge mainline to release and follow with the release and publish jobs.
What is the impact of this change?
Should make release process smoother
How was this change tested?
Tested in a developer github account
Was this change documented?
no
Is this a breaking change?
no