This is a practice adopted in several actions I've actively contributed to maintaining in the jupyterhub org, and it has been working great for a few years now without any maintenance requirements for the added automation either.
With this automation, cutting a v1.2.3 release for example leads to updating a v1 tag as well, and that allows people to pin to v1 instead of v1.2.3 etc.
This is a practice adopted in several actions I've actively contributed to maintaining in the jupyterhub org, and it has been working great for a few years now without any maintenance requirements for the added automation either.
With this automation, cutting a
v1.2.3release for example leads to updating av1tag as well, and that allows people to pin tov1instead ofv1.2.3etc.