at this point you're better off writing your own action, aren't you? What kind of platform limits the format of the tags you can use on git?

at this point you're better off writing your own action, aren't you? What kind of platform limits the format of the tags you can use on git?

Sorry, I should have been more clear. In .NET and Windows ecosystem apps have to follow assembly versioning format. Notepads is one such app, and you are right there is no limitation to create semver tags but we chose to keep the tags similar to version of the app to avoid confusion. And yes, it is possible to write a separate action for this purpose, but I found with minimal change this action can fulfill this request without breaking anything which I implemented in #73. In the end, it's totally up to you whether you want to implement it or not.

Honestly, even if the implementation doesn't break stuff now, it's adding complexity that we need to maintain in the long run.

Looking at your repo, it seems like the tags are always x.x.x.0. Maybe it'd be easier to simply use semver and add a trailing 0 when needed 😄

Honestly, even if the implementation doesn't break stuff now, it's adding complexity that we need to maintain in the long run.

The only thing I can offer is my help in maintaining this action, since we use this in our repo we are glad to offer you help for maintaining it.

Looking at your repo, it seems like the tags are always x.x.x.0. Maybe it'd be easier to simply use semver and add a trailing 0 when needed 😄

Since Notepads is in early stage of development we now follow this version format, as the app matures and we will change the revision to other values.

The way we want to use this action is to calculate x.x.x from the commits and if it matches the previous version then increase .x (kind of our own default_bump implementation) appended later otherwise use tag in x.x.x.0 format.

To reiterate, you are free to choose to not implement it, I am ok with it either way.