🚤 Keep your action versions up-to-date by automatically promoting a major tag (and optionally, a latest tag) each time a release is created.

According to the github actions versioning guide, actions publishers should have a major tag (v1, v2, etc) which points to the latest version of any minor/patch release of their action, for ease of use by the others.

I found this process quite tedious, and repetetive which is why this action exists. If you have published an action and would like to have your action follow the same versioning structure as many others in the marketplace, then simply create a release workflow that includes this action. See the usage example.

Indicates to the action whether or not to create/update a tag called latest pointing to the latest release. Default: "false".

Do you prefer creating vN branches or vN tags? Default: "false"

A github token used for creating an octoclient for making API calls. Default: ${{ github.token }}.

The version of the branch/tag that was published/updated.

Was latest also published?

Deprecated in v3: Use tag

Deprecated in v3: If a non-default PAT (Personal Access Token) is needed, use token instead.

This action supports debug logging. When enabled, it will dump the output of the api call for creating the tags/branches. This is useful for testing and should be included when reporting bugs.

versioning.yml

name: Keep the versions up-to-date

on:
  release:
    types: [published, edited]

jobs:
  actions-tagger:
    runs-on: windows-latest
    steps:
      - uses: Actions-R-Us/actions-tagger@latest
        with:
          publish_latest_tag: true

Note this action is able to detect if it is being run in a release context, and if not it will notify you and exit gracefully.

• Creates a latest tag