The build workflow seems to refer to
run: echo "cppcheck_tag=$(curl -s https://api.github.com/repos/danmar/cppcheck/releases/latest | jq .tag_name)" >> $GITHUB_OUTPUT
https://github.com/cppcheck-opensource/cppcheck is the correct repo.
https://api.github.com/repos/cppcheck-opensource/cppcheck/releases/latest. There is currently a redirect, so it isn't broken.
However, slightly futher down:
curl -s https://api.github.com/repos/danmar/cppcheck/releases/latest | jq .tarball_url
This resolves to NULL.
curl -s https://api.github.com/repos/danmar/cppcheck/releases/latest | jq .tarball_url
null
That is broken.
curl -s https://api.github.com/repos/danmar/cppcheck/releases/latest
{
"message": "Moved Permanently",
"url": "https://api.github.com/repositories/143131/releases/latest",
"documentation_url": "https://docs.github.com/rest/guides/best-practices-for-using-the-rest-api#follow-redirects"
}
The build workflow seems to refer to
https://github.com/cppcheck-opensource/cppcheck is the correct repo.
https://api.github.com/repos/cppcheck-opensource/cppcheck/releases/latest. There is currently a redirect, so it isn't broken.
However, slightly futher down:
curl -s https://api.github.com/repos/danmar/cppcheck/releases/latest | jq .tarball_urlThis resolves to NULL.
That is broken.