Although gha-scala-library-release-workflow is already used by many repos at the Guardian, and in other projects, this is the first time I've git-tagged the repo to identify a release of the workflow itself!
The release strategy is informed by GitHub's documentation on versioning actions :
- Create ... the release tag (for example, v1.0.2).
- Create a release using semantic versioning.
- Move the major version tag (such as v1, v2) to point to the Git ref of the current release. For more information, see "Git basics - tagging."
- Introduce a new major version tag (v2) for changes that will break existing workflows. For example, changing an action's inputs would be a breaking change.
Accordingly, I'll create the tag v1 to point to v1.0.0 - for now:
git tag -f v1 v1.0.0 && git push origin v1 -f