search

containerd / project-checks

This cross-project repository holds utilities, scripts, and common files used across the containerd master project and many sub-projects within the containerd organization
Apache License 2.0
5 stars 10 forks source link

Resolve proper way to handle tags/versioning of action #2

Open estesp opened 3 years ago

estesp commented 3 years ago

See this comment for the canonical (?) way to handle making small fixes while allowing consumers to still use a "major" reference like v1: https://github.community/t/version-numbering-for-actions/16307/5

estesp commented 3 years ago

Would love your thoughts here @mxpv ; I created a v1.0.1 tag to make progress on the website repo using this action, but don't want to make too much mess before we figure out how to handle small fixes in the future.

mxpv commented 3 years ago

I think the suggestion you referenced is a good one, I haven't seen before. In current approach with tags, every time we make a new release (like v1.0.1), we have to repush v1 tag to point it from v1.0.0 to v1.0.1, so runners pick up a new change. In case of v1 branch we don't have to do that, but rather just push a change directly to that branch. Otherwise we just push stuff to master branch and it won't be picked up by anyone (unless there is containerd/project-checks@master somewhere).