Add tags for minor/major versions of the action.

[Ferroin]

Currently, this action just provides a single tag per release, matching the exact version published. Due to the frequency of updates, and the fact that documentation-only updates appear to be common, this leads to a nontrivial amount of disruption for anybody using Dependabot or a similar dependency tracking service to keep their GitHub Actions workflows up to date.

A number of other actions, most notably including all of those provided by GitHub itself, also provide tracking tags for specific major or minor versions to mitigate this issue, removing the need to update at all until a new major or minor version is published.

As an example, for the actions/checkout action, you can use any of the following tags:

• v4.1.7: The exact current version of the action, just like what this action is providing currently.
• v4.1: The latest version such that the version is at least v4.1 but strictly less than v4.2.
• v4: The latest version such that the version is at least v4 but strictly less than v5.

Almost all actions recommend use of the second or third type of tag, because it limits the frequency of changes needed to track the latest version.

[japarson]

Hi @Ferroin , thank you for bringing this up. This is my first time maintaining a GitHub Action so I really appreciate the explanation of how tag versioning is supposed to work. I'll work on implementing this system for future releases.

[Jaxelr]

@japarson what @Ferroin is suggesting is that we create multiple tags on specific versions, you can see an example of what he means on either the checkout or the stale repos.

[japarson]

@Ferroin I've added tags for v0 and v0.5 which point to the current latest version v0.5.1 and I'll maintain these tags in the future. I'm sorry this took so long.