jq is not available on all self-hosted runners
When version: latest-release is used (which is the default), the action relies on jq to parse the GitHub API response. If jq is not installed on the runner, the action fails with:
++ jq -r .tag_name
/home/user/actions-runner/_work/_temp/b77ba04b-c6db-4240-9055-9d664e2a0c25.sh: line 18: jq: command not found
Error: Process completed with exit code 127.
jq is not a standard tool guaranteed to be present on all systems — it is common on GitHub-hosted runners but may be missing on self-hosted ones.
The action should not depend on it without checking for its availability or providing a fallback.
setup-ko version: v0.9
jq is not available on all self-hosted runners
When version: latest-release is used (which is the default), the action relies on jq to parse the GitHub API response. If jq is not installed on the runner, the action fails with:
jq is not a standard tool guaranteed to be present on all systems — it is common on GitHub-hosted runners but may be missing on self-hosted ones.
The action should not depend on it without checking for its availability or providing a fallback.
setup-ko version: v0.9