v1

Soliciting thoughts on an idea I put forward in #47 - what if we started versioning this repository? We could then pass a "major version" tag to each new minor or patch commit. All workflow references would use the major version tag as their reference point, so minor and patch updates would passively be consumed. Breaking changes to the workflows would trigger a major version update, meaning the downstream repos would keep using the previous major version until a manual update was applied. Could open the door to automated updates, if we have a tool that can check for new major version tags. The general process would look like:

1. New commit aabbcc, creating version 1.0.0
2. Commit aabbcc is tagged with v1.0.0 and v1
3. New commit ddeeff moves to version 1.0.1
4. Commit ddeeff is tagged with v1.0.1
5. Tag v1 is moved to commit ddeeff (downstream workflows relying on tag v1 now pull this commit)
6. New commit xxyyzz creates version 2.0.0
7. Commit xxyyzz is tagged with both v2.0.0 and v2 (meaning downstream workflows keep pulling commit ddeeff until manually updated)