Paul Hatcherian

The new behavior for version 5 going forward will be to sort by the version number itself rather than the date. This should be sufficient to cover edge cases here....

Sorry I missed this question until now, but just in case some one else comes across it, you are correct with the current implementation. In v5.0.0 the branch must be...

Release [v5.0.0-beta](https://github.com/PaulHatch/semantic-version/releases/tag/v5.0.0-beta) includes an update from @dusda to use the latest version of actions/core which internally uses the new method to set outputs.

Hey @ianbondoc, thanks for this report, I have been traveling and have not had a chance to look at this until today, but in the meantime you might consider using...

Closing. I have not been able to reproduce this for any version of this action, for example using the latest: ``` - uses: paulhatch/[email protected] id: version with: change_path: "project/path" -...

So this action is going to be running entirely on the local copy of the repo, so any concurrency issues will need to be handled higher in the "stack". Having...

Hey @Hathoute, yes, sorry I've been traveling + moving internationally, and just getting settled back in now after a crazy couple of weeks. There's a new tagged version, [v5.0.0-beta](https://github.com/PaulHatch/semantic-version/releases/tag/v5.0.0-beta), which...

Sorry, I'm not familiar with this build-and-tag action, but if I understand what you're saying on this line correctly: > move the git tag to the new commit produced, on...

There is not currently a way to specify this in the config, though you can just tag any previous commit `v2.0.1` to set the last version and the action will...

If your tag is just `2.0.1` you need to specify that the `tag_prefix` is and empty string, as the default is `"v"` and it will be looking for a tag...