-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Last tag resolved to previous one instead #9
Comments
The git was just pushed with 0.1.2 tag, so it should be there I've linked the workflow above: https://github.com/symplify/github-actions/runs/1491326330?check_suite_focus=true#step:4:108 |
Ow ah doh my bad. Was looking for it at the bottom, not at the top. Found that the workflow runs on |
Thanks for tips! The split should happen on both commit and tagging, so tags and dev-master are split. I've tried to add something in last 3 commits: I've added new tag 0.1.3 here: Seems it's working :) Could you give me some feedback on last 3 commits? What to improve there? |
This is the best approach I came with so far :) |
This also happened on our repository: https://github.com/linode/linode-cli/actions/runs/11578534127/job/32232579882 |
@zliang-akamai The PR @epm-marcus created today might help as well: #56 Looking at it now |
Hi,
thank you for the tagging Action. I've been looking for this one for ages.
It works well. We're having small issues on tag release.
We've just released a 0.1.2 here:
https://github.com/symplify/github-actions/runs/1491326330?check_suite_focus=true#step:4:108
But version was resolved to 0.1.1:
How can we get the latest tag 0.1.2 insted?
Thank you
The text was updated successfully, but these errors were encountered: