Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add tags like `v1` etc

See original GitHub issue

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.

Issue Analytics

State:
Created 4 years ago
Reactions:10
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

XhmikosRcommented, Dec 28, 2021

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.

0reactions

XhmikosRcommented, Dec 28, 2021

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.