Semantic Release running twice on the same commit should have the same output

[alinalex1392]

I have the following configuration on the semantic release:

const branch = process.env.CI_COMMIT_REF_NAME
const name = process.env.DOCKER_URI
const issuePrefix = process.env.ISSUE_PREFIX
const issueUrlFormat = process.env.ISSUE_URL_FORMAT

const config = {
  branches: [
    '+([0-9])?(.{+([0-9]),x}).x',
    'main',
    {
        name: 'feature/*',
        prerelease: '${name.replace(/^feature\\/(.*?-\\d+)/g, "$1")}'
    },
    {
        name: 'fix/*',
        prerelease: '${name.replace(/^fix\\/(.*?-\\d+)/g, "$1")}'
    }
  ],
  plugins: [
    ["semantic-release-unsquash", {
      "commitAnalyzerConfig": {
        "preset": "conventionalcommits",
      },
    },
    ],
    [
        "@semantic-release-plus/docker",
      {
        "name": name,
        "publishChannelTag": false,
        "skipLogin": true,
      }
    ]
  ],
}

if (!branch.startsWith('feature') && !branch.startsWith('fix')) {
  config.plugins[0][1] = {
    ...config.plugins[0][1],
    "notesGeneratorConfig": {
        "preset": "conventionalcommits",
        "presetConfig": {
          "issuePrefixes": [issuePrefix],
          "issueUrlFormat": issueUrlFormat,
        }
    }
  }
  config.plugins.push(
  [
    "@semantic-release/changelog",
    {
      "changelogFile": "CHANGELOG.md",
      "changelogTitle": "# Changelog"
    }
  ],
  ["@semantic-release/git", {
    "assets": ["CHANGELOG.md"],
    "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
  }])
}

module.exports = config

Actions:

1. Create a branch using the pattern feature/*
2. Modify something in the microservice that should trigger a docker build and commit with a message on the pattern fix:* or feat:*.
3. Open a merge request.

In the back two pipelines will run in parallel:

• One for branch, where the release version is computed correctly
• One for MR, the docker plus plugin sees the tag already present because of the branch build and is picking the image version with the CI_PIPELINE_ID instead of the one with the tag found.
  Currently to mitigate this issue, just make a new commit on the branch. Right now the pipeline will run only on the MR and the version will be computed correctly.

Is there a way to get on the MR workflow that happens after the branch workflow, the current tag from the semantic release?

The semantic release knows the tag but is not tagging my docker image anymore.

[12:39:49 PM] [semantic-release] › ✔  Allowed to push to the Git repository
[12:39:49 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release-plus/docker"
[12:39:49 PM] [semantic-release] [@semantic-release-plus/docker] › ℹ  Skipping docker login because skipLogin was set to true
[12:39:49 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release-plus/docker"
[12:39:49 PM] [semantic-release] › ℹ  Found git tag v1.12.2-INDIGO-9999-test-3.1 associated with version 1.12.2-INDIGO-9999-test-3.1 on branch feature/INDIGO-9999-test-3
[12:39:49 PM] [semantic-release] › ℹ  Found 0 commits since last release
[12:39:49 PM] [semantic-release] › ℹ  Start step "analyzeCommits" of plugin "semantic-release-unsquash"
[12:39:49 PM] [semantic-release] [semantic-release-unsquash] › ℹ  Analysis of 0 commits complete: no release
[12:39:49 PM] [semantic-release] › ✔  Completed step "analyzeCommits" of plugin "semantic-release-unsquash"
[12:39:49 PM] [semantic-release] › ℹ  There are no relevant changes, so no new version is released.

In order to have builds in the MR I use semantic-release --no-ci flag