/claude Please look at the Github workflow templates under template/.github/workflows and note how they call cross-repo workflows (maintained in this repository, under .github/workflows) at a specific version injected by Copier ({{ _commit }}). We would like to use a floating version tag instead of the exact version tag for calling cross-repo workflows so that they can be updated independently of copier update runs on the various repositories generated from the template. Ideally, we would have a semantic tagging scheme, like gha-1.0, gha-1.0.1, gha-1.1, etc... with the floating tag gha-1 pointing at the latest workflows release tag. We already do something similar in our documentation; see template/documentation/contribution.rst.jinja for details. Please propose the necessary changes to make this happen. (Only files under template/.github/workflows should need to be modified; please do not attempt modifications to any files under .github/workflows.)
/claude Please look at the Github workflow templates under
template/.github/workflowsand note how they call cross-repo workflows (maintained in this repository, under.github/workflows) at a specific version injected by Copier ({{ _commit }}). We would like to use a floating version tag instead of the exact version tag for calling cross-repo workflows so that they can be updated independently ofcopier updateruns on the various repositories generated from the template. Ideally, we would have a semantic tagging scheme, likegha-1.0,gha-1.0.1,gha-1.1, etc... with the floating taggha-1pointing at the latest workflows release tag. We already do something similar in our documentation; seetemplate/documentation/contribution.rst.jinjafor details. Please propose the necessary changes to make this happen. (Only files undertemplate/.github/workflowsshould need to be modified; please do not attempt modifications to any files under.github/workflows.)