Duplicate Tags - How to skip to a new version

Hello,

We are using gitlab and semantic-release and semantic-release/gitlab plugin to do version tagging / creating releases.

Our pipeline was broken by someone manually adding tags (without the associated release in gitlab), so we are now in a situation where our pipeline using semantic-release is trying to create version tag 1.1.0-develop.25 but we are up to 1.1.0-develop.36

We have been manually doing the pipeline job since v25 (the devs were unaware of semantic-release, let alone how it worked and needed to get builds out).

We created a release manually in gitlab on the v25 tag, however the semantic-release script is still trying to create v25.

Is there a way to manually do the releases in gitlab to convince semantic-release to use the latest version?

I have seen semantic-release uses git notes to store current version info, I guess that the gitlab plugin uses the gitlanb releases instead to maintain the version info? There are no results for git notes list on our repo.

Thanks

Start by reviewing the semantic-release version and tag handling described in the issue, then inspect the GitLab plugin's release documentation and related implementation. Confirm whether manually created GitLab releases or Git tags affect the next calculated version, and document the supported recovery procedure or the missing behavior.