Fix latest semver tag retrieval for first time setup #160
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think tagpr v1.1.3 has a breaking change; when Songmu/tagpr is first setup, the Semver tag retrieval fails and returns
""
.For example, the hatenablog-workflows repository which already has some tags tried to setup tagpr but ended up with the following Pull Request:
This is probably because of #159 ; once you setup
.tagpr
file manually it works, but first time setup there is no.tagpr
solatestSemverTag
fails.I attempted to fix the problem by adding a condition check; if the config is defined check the vPrefix, otherwise return the first value (v1.1.2 behavior).
Here is some example code to show what I want to do: https://go.dev/play/p/OgCCpuethSr