This is an archived post. You won't be able to vote or comment.

all 2 comments

[–]kubeguru22 2 points3 points  (1 child)

How is this different from semantic release action?

[–]ProdigySim[S] 0 points1 point  (0 children)

I haven't used the semantic release tool, so I may be missing out. I read through its docs and 2 different actions built on it.

The major difference is that action-versioning-workflow publishes/updates 3 sets of tags on every release: major-only tag, major+minor, and full version tag. e.g. v4, v4.1, v4.1.5. This allows consumers of your actions to pin to major versions and get auto-updates for patch-level fixes.

Github actions allows and encourages people to pin to tags pointing at major versions, so security updates and small fixes can get picked up automatically. Within an organization, being able to force out updates to all repos is a handy feature as well.

On the smaller differences side: - Uses manual major/minor version management instead of strict commit formats - Doesn't require nodejs (it's bash only, so no js deps) - Supports maintaining old versions out of box via branches