-
Notifications
You must be signed in to change notification settings - Fork 1
Workflow Tagging
Ryan Slominski edited this page Apr 10, 2024
·
4 revisions
Workflows are versioned in semver just as with regular software, however, the GitHub Action workflows convention is to reference a major version number such that backwards compatible minor and patch updates are received automatically. This means we need a tag similar to the DockerHub "latest" tag that moves with each release. It actually looks like "v1" or "v2" or "v3", etc. This should probably be automated, but at the moment it requires manual intervention after each release.
Steps to move it (showing v1 as example):
git tag -f v1
git push --tags -f
Note: Force pushing a tag update will trigger the CD workflow all over again if not careful. See: https://github.com/JeffersonLab/container-workflows/issues/2