-
Notifications
You must be signed in to change notification settings - Fork 32
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
same error as issue #20 in version v0.4.4 #40
Comments
Tags or actual GitHub release? They aren't treated the same in the GitHub API. If they are just tags, try turning the desired tag into a release and see if that fixes the issue. |
It's a fork, and the previous "releases" are all tags. They're obviously different "things" but github does show both releases and tags in the "release" column. Anyway, I went ahead with a more flexible/forgiving solution using gitchangelog instead. This seems like a good candidate for a readme update. |
Thanks for the detail. Hopefully this #42 covers it. |
In a repository with several (pre-release) tags I'm getting this:
when trying to create a new release (not a pre-release) using github actions. Looking at the closed bug I still can't figure out what the "correct" usage is.
The text was updated successfully, but these errors were encountered: