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
https://github.com/uutils/coreutils/releases/tag/0.0.29 did not publish binaries in assets. Is there something broken?
According to https://github.com/uutils/coreutils/actions/runs/12844591541/job/35817804155, the Publish step was skipped, because the workflow was not triggered by a tag.
GITHUB_REF=refs/heads/main steps.vars.outputs.REF_TAG= steps.vars.outputs.DEPLOY=
coreutils/.github/workflows/CICD.yml
Line 550 in 64dad0c
Lines 575 to 577 in 64dad0c
Lines 781 to 783 in 64dad0c
In the 0.0.28 release, https://github.com/uutils/coreutils/actions/runs/11872661297 was triggered by the tag 0.0.28, and https://github.com/uutils/coreutils/actions/runs/11872414805 was triggered by main. The former published binaries.
0.0.28
main
GITHUB_REF=refs/tags/0.0.28 steps.vars.outputs.REF_TAG=0.0.28 steps.vars.outputs.DEPLOY=true
The text was updated successfully, but these errors were encountered:
github.com/uutils/coreutils
split -C ...
No branches or pull requests
https://github.com/uutils/coreutils/releases/tag/0.0.29 did not publish binaries in assets. Is there something broken?
Possible cause
According to https://github.com/uutils/coreutils/actions/runs/12844591541/job/35817804155, the Publish step was skipped, because the workflow was not triggered by a tag.
coreutils/.github/workflows/CICD.yml
Line 550 in 64dad0c
coreutils/.github/workflows/CICD.yml
Lines 575 to 577 in 64dad0c
coreutils/.github/workflows/CICD.yml
Lines 781 to 783 in 64dad0c
In the 0.0.28 release, https://github.com/uutils/coreutils/actions/runs/11872661297 was triggered by the tag
0.0.28
, and https://github.com/uutils/coreutils/actions/runs/11872414805 was triggered bymain
. The former published binaries.The text was updated successfully, but these errors were encountered: