Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Duplicate Tags - How to skip to a new version #760

Open
stringy05 opened this issue Aug 19, 2024 · 6 comments
Open

Duplicate Tags - How to skip to a new version #760

stringy05 opened this issue Aug 19, 2024 · 6 comments
Labels
support

Comments

@stringy05
Copy link

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
@gravypower
Copy link

+1 this has happened for me also

@fgreinacher
Copy link
Contributor

Can one you please provide a minimal project on GitLab.com that shows this behavior? That would really help us understand the situation better. 🙇

@stringy05
Copy link
Author

Not without some significant effort, it's an internal repository.

I guess what would be really useful is to know where sematic-release sources the current version number from, is it purely the releases in gitlab, or is there some extra place it is looking as well?

@travi
Copy link
Member

travi commented Sep 26, 2024 •
edited
Loading

semantic-release uses tags and git notes to manage versions and what has been released in which channel. from your mentioned versions, it looks like you are using gitflow with out prerelease workflow (which, btw, is not officially supported), so you will need to repair both to recover from the situation you are in. you can find details about how to do so in our docs at:

@stringy05
Copy link
Author

does it use git notes when I'm using the gitlab plugin? If I run git notes on the repo in question there is no output eg:

$ git notes
$ echo $?
0
$ git notes list
$

@travi
Copy link
Member

travi commented Oct 25, 2024

git notes are used by the core of semantic-release to track which distribution channels a version has been released to. if you are only releasing to your default channel from your default branch, notes are not important. they are much more important for pre-releases and maintenance release workflows

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
support
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@travi @fgreinacher @gravypower @stringy05