Automatically roll latest version tag

[davidmfinol]

Changes

• Automatically roll v1 whenever a new release tag is published. Closes Unable to resolve action game-ci/steam-deploy@v1, unable to find version v1 #27.

Checklist

• Read the contribution guide and accept the code of conduct
• Readme (updated or not needed)
• Tests (added, updated or not needed)

[webbertakken]

Yup

[webbertakken]

Didn't seem to work after editing the release, even though reading the triggers documentation I had expected this to work.

[webbertakken]

Trying to fix in #30

[webbertakken]

Reverted in #31

Rolling next minor version instead.

[webbertakken]

Still does not work, with the warning This action can only operate on semantically versioned releases, however we probably don't want to publish patch level for a simple action like this.

I also do not see a difference in unity builder's versioning workflow, just that we use a more complicated tag (v2.0-alpha-13) there. Which technically is also not a 3 digit semantic version either.

I believe 2 digit versions are quite common in actions, not sure if we should switch everything to 3 digit semantic versioning.
Any thoughts?

[davidmfinol]

I think we should use 3 digit semantic versioning everywhere, where we leave the patch version as 0 most of the time.

For example, can we try v1.2.0 and see if that works?
If it does, we could have the next release be v1.3.0 and so on.

[webbertakken]

https://www.npmjs.com/package/semver#user-content-coercion should work for us.

However it is currently only done for prereleases (see here).

To make it work for non-prerelease v[Major].[Minor] and deduce [Patch] we will need this.

Forking the action.

[webbertakken]

I think we should use 3 digit semantic versioning everywhere, where we leave the patch version as 0 most of the time.

For example, can we try v1.2.0 and see if that works? If it does, we could have the next release be v1.3.0 and so on.

Or that.

[webbertakken]

Since rule 2 of semantic versioning dictates that a normal version number MUST have three digits, I think your suggestion is better @davidmfinol.

Let's move to full semver for all our repos to solve the problem across the board.

Tagging one additional version to close this issue.