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 added by 'git notes add' -- author: semantic-release-bot

Is there any way to avoid this?

Here's my config:

    "release": {
        "plugins": [
            "@semantic-release/commit-analyzer",
            [
                "@semantic-release/changelog",
                {
                    "changelogFile": "CHANGELOG.md"
                }
            ],
            [
                "@semantic-release/npm",
                {
                    "npmPublish": false
                }
            ],
            [
                "@semantic-release/git",
                {
                    "assets": ["CHANGELOG.md"]
                }
            ]
        ]
    },

question from:https://stackoverflow.com/questions/65872655/avoiding-2nd-semantic-release-commit-on-bitbucket-cloud

Answer 1

Waitting for answers