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.

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

tag cannot be found #48

Open
acnicholls opened this issue Nov 5, 2024 · 2 comments
Open

tag cannot be found #48

acnicholls opened this issue Nov 5, 2024 · 2 comments

Comments

@acnicholls
Copy link

i have a repo with several dotnet projects in it.
the projects are in different folders, so I built pipelines to pack Nugets for each folder.
the pipelines with checkout the repo, find the next version, build it, pack it and push
I am trying to use your action to get the next version of the Nuget based on a prefixed tag.

the problem I am having is that there are other tags in the repo and my latest for one folder's Nuget is not within the top 10 latest tags.

I have tried using fromTag to go back to the first tag for the NuGet, but that didn't work, I also tried settings maxTagsToFetch to 2000 (which is more than I have tags in that repo), but that didn't work either

How can I fix this issue?

@NGPixel
Copy link
Member

NGPixel commented Nov 5, 2024

Are your tags valid semver without the prefix? For example, if you set the prefix to foobar/, then your tags should be foobar/1.0.0 or foobar/v1.0.0.

Using fromTag won't do what you expect since it will fetch all tags from that tag, regardless of the prefixes.

Also, the GitHub API doesn't allow to fetch more than 100 tags at a time. So setting it 2000 won't work.

@acnicholls
Copy link
Author

acnicholls commented Nov 5, 2024

My tags are valid, the problem is that I also tag every push to develop with stage.v9.9.9, so i have just under a hundred of those tags on top of several web-nuget.v9.9.9 and data-nuget.v9.9.9, but they are not found when this action tries to find current version to calc next version.

the web and data nuget tags were started earlier around stage tag 67 and last night I was on stage tag 75, so there aren't really that many tags between, but there are a lot of commits. What I ended up doing was just adding a tag to a newer commit that was one later than the previous one and re-ran the workflow, both nugets were created with tags, etc.

stage tag 67 was 2024-10-09
web nuget tag v1.0.0 was 2024-10-26
web nuget tag v1.0.1 was 2024-10-31

and there are at least a hundred or more commits between stage-67 and web-101.

EDIT: updated from mobile made comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants