We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A common pattern for actions is to always create a tag for the major version, such as v1, v2 and etc. which this action is missing.
v1
v2
Could that be implemented? There are several actions that can take care of that automatically when new tags following semver are released.
The text was updated successfully, but these errors were encountered:
Hey @ldaneliukas,
will take care about this after the v2.3.0 release
v2.3.0
Sorry, something went wrong.
No branches or pull requests
A common pattern for actions is to always create a tag for the major version, such as
v1
,v2
and etc. which this action is missing.Could that be implemented? There are several actions that can take care of that automatically when new tags following semver are released.
The text was updated successfully, but these errors were encountered: