You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some small projects might decide not to release patch versions but still follow the semantic versioning rules. Can this action work with tag-semver: v${{major}} on tags like v1.0 to produce v1? Currently, it does not seem to:
A normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes. X is the major version, Y is the minor version, and Z is the patch version. Each element MUST increase numerically. For instance: 1.9.0 -> 1.10.0 -> 1.11.0.
Should have been v1.6.0 to be a valid one for example. I will add a warning message in case tag-semver is used but input tag is not a valid semver.
Some small projects might decide not to release patch versions but still follow the semantic versioning rules. Can this action work with
tag-semver: v${{major}}
on tags like v1.0 to producev1
? Currently, it does not seem to:https://github.com/EnricoMi/publish-unit-test-result-action/runs/1474478085?check_suite_focus=true
The text was updated successfully, but these errors were encountered: