Avoiding 2nd semantic-release Commit on Bitbucket Cloud

Question

I\'m using Bitbucket Cloud and everything works wonderfully using pipelines, except I always get an extra commit after my release/tag commit, as follows:

Notes adde