Pin container images in action.yaml for each git tag pushed

[sgibson91]

It would be good to pin a particular version here (the action.yaml file).

I'm guessing the standard way to do this is put our "current" version here, then push the tags when we merge to main?
So that when someone writes workflow like

  - uses: the-turing-way/all-all-contributors@v1

It fetches this repo at a particular tag, and hence the corresponding container image tag from this file?

Originally posted by @JimMadge in #66 (comment)

[sgibson91]

It fetches this repo at a particular tag, and hence the corresponding container image tag from this file?

Yes, that is the correct assumption. But I don't know how to achieve this flow without some complex manual git commands. For every tag we push, the tag would need to be listed in the action.yaml file as well, it would be nice if there was a reference we could use that automated this a bit more.

There is a similar issue with helm charts that are dependent on (multiple) image versions. The JupyterHub team ended up writing a bespoke python package to handle this kind of "we want to insert a specific version tag into this specific build" kind of problem https://github.com/jupyterhub/chartpress Hence you see things like {{ set-by-chartpress }} in values files that gets updated: https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/63fde8dfc4bb28fd2e52e658aa2e0d853a2b4a45/jupyterhub/Chart.yaml#L4
Workflow: https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/63fde8dfc4bb28fd2e52e658aa2e0d853a2b4a45/CONTRIBUTING.md#4-build-images-update-values-install-chart