coverallsapp
Add tags like `v1` etc
Many official GitHub Actions follow this scheme. This allows people to have better control on the action. Using master can break at any time, while using a tag shouldn't break without updating the major version.
For example https://github.com/actions/setup-node/releases or https://github.com/actions/checkout/releases
BTW I'm not sure how they automate the release process, but I can't imagine this is done by hand, i.e. recreating the tag manually.
Just as a reference: https://docs.github.com/en/actions/creating-actions/about-actions#using-tags-for-release-management
Looking at https://github.com/coverallsapp/github-action/releases now, it seems that there are Git tags and then maybe this ticket can be closed as fixed?
Nope, there is no v1 tag. The idea is to give people the ability to point to a major version tag without having to update their workflows for each minor/patch version.
Nope, there is no
v1tag. The idea is to give people the ability to point to a major version tag without having to update their workflows for each minor/patch version.
Maybe we're talking about two different things. If you look at https://github.com/actions/setup-python/tags , they have both v1 and v2 Git tags, where v2 is moved every now and then. It's not something I would do and recommend personally, but it's a workaround that is in use in the wild to implement a semver-like approach with little need for frequent updates, and that repository is proof (and not the only one).
We are talking about the same thing. This action here does not publish semver major tags on each mino/patch release, which is exactly what this issue is about.
Hey! Now there is a v1 tag. Please mention me if you feel a need for minor tags like v1.1 and v1.2
@mrexox thanks for this! That being said, the process should be automated so that v1, v2 tags are created automatically.