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
Currently the tags are all named x.y.z, except for v2.1.0 and v2.1.1 (they have a leading v). Note, that the workflows are contradicting:
x.y.z
v2.1.0
v2.1.1
v
release
cargo-valgrind/.github/workflows/release.yaml
Line 9 in 23f798d
Line 14 in 23f798d
Line 26 in 23f798d
deploy
cargo-valgrind/.github/workflows/deploy.yml
Line 6 in 23f798d
This causes the latest release to not include any artifacts.
The text was updated successfully, but these errors were encountered:
Always use the x.y.z tag scheme (without v)
2fdf90f
Fixes #88.
d5bc691
Successfully merging a pull request may close this issue.
Currently the tags are all named
x.y.z
, except forv2.1.0
andv2.1.1
(they have a leadingv
). Note, that the workflows are contradicting:release
-workflow forces a tag name without thev
:cargo-valgrind/.github/workflows/release.yaml
Line 9 in 23f798d
cargo-valgrind/.github/workflows/release.yaml
Line 14 in 23f798d
cargo-valgrind/.github/workflows/release.yaml
Line 26 in 23f798d
deploy
-workflow only runs on a tag name with thev
:cargo-valgrind/.github/workflows/deploy.yml
Line 6 in 23f798d
This causes the latest release to not include any artifacts.
The text was updated successfully, but these errors were encountered: