This workflow automatically recreates a new major version tag each time a semantic version of this module is tagged
I haven't bothered to create a new minor version as well, as I think it's more then what's actually required in the real-world
Here's an example of why we need this workflow - https://github.com/silverstripe/silverstripe-campaign-admin/actions/runs/1965267629 - the issue this run had was patched in 0.1.16 of silverstripe/github-action-ci-cd, however the module only requires ci.yml@^0.1.15. After merging this pull-reqest, we can update campaign-admin (and other js modules) to instead require ci.yml@v0.1
Issue - https://github.com/silverstripeltd/product-issues/issues/367
carets (^) do not work in github actions for getting the latest semantic version of an action e.g. @^2 doesn't work
Instead, what needs to be done is to tag a new 'major' version each time, so that it can instead be required as @v2
This is consistent with what github actions/checkout does - https://github.com/actions/checkout/tags
This workflow automatically recreates a new major version tag each time a semantic version of this module is tagged
I haven't bothered to create a new minor version as well, as I think it's more then what's actually required in the real-world
Here's an example of why we need this workflow - https://github.com/silverstripe/silverstripe-campaign-admin/actions/runs/1965267629 - the issue this run had was patched in 0.1.16 of silverstripe/github-action-ci-cd, however the module only requires ci.yml@^0.1.15. After merging this pull-reqest, we can update campaign-admin (and other js modules) to instead require ci.yml@v0.1
Example of this workflow running on a made up tag 3.2.2: https://github.com/emteknetnz/github-actions-ci-cd/actions/runs/1996324988 v3 tag
Example of this workflow failing when it's supposed to on a 3.2.3-beta1 tag: https://github.com/emteknetnz/github-actions-ci-cd/actions/runs/1996326747