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
{{ message }}
Repository navigation
[BUG] asyncapi/cli@v6.3.0 action fails: Docker image asyncapi/github-action-for-cli:6.3.0 not found #2345
asyncapi/cli@v6.3.0 cannot run: the job fails while pulling the action's Docker image, because asyncapi/github-action-for-cli:6.3.0 does not exist on Docker Hub.
action.yml at tag v6.3.0 hardcodes the image to the release version (a comment in the file says it is generated during the Changesets version PR):
This hardcoded rule ties every action tag to a same-named tag of a separate repository (asyncapi/github-action-for-cli, not asyncapi/cli). If that one image is not published, the tag is broken. Related facts:
The release workflow publishes asyncapi/github-action-for-cli:6.3.0, so uses: asyncapi/cli@v6.3.0 works.
Screenshots
Pull down action image 'asyncapi/github-action-for-cli:6.3.0'
/usr/bin/docker pull asyncapi/github-action-for-cli:6.3.0
Error response from daemon: failed to resolve reference "docker.io/asyncapi/github-action-for-cli:6.3.0": docker.io/asyncapi/github-action-for-cli:6.3.0: not found
Error: Docker pull failed with exit code 1
How to Reproduce
Use uses: asyncapi/cli@v6.3.0 in any GitHub Actions workflow (e.g. via a Dependabot bump from v6.2.3).
Run the workflow.
The job fails at "Set up job" with the pull error above. Pinning back to v6.2.3 works.
🖥️ Device Information [optional]
Operating System (OS): GitHub-hosted runner, ubuntu-26.04
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
The CLI image does exist: asyncapi/cli:6.3.0 is on Docker Hub. Only the action image asyncapi/github-action-for-cli:6.3.0 (used by action.yml) is missing.
The Release Docker Image run for v6.3.0 ended as cancelled after 6h: https://github.com/asyncapi/cli/actions/runs/42328838823. The workflow publishes asyncapi/cli first and the action image (./github-action/Dockerfile) afterwards, so it looks like the first image was pushed and the second was never built. The v6.2.3 run succeeded in ~32 min.
Re-running that workflow (or pushing the image manually) should fix asyncapi/cli@v6.3.0 for everyone.
Question: why are there two separate Docker Hub repositories (asyncapi/cli and asyncapi/github-action-for-cli), and why does the action use the separate wrapper image rather than asyncapi/cli? Having a second image to publish makes releases like this one fragile, since a partially failed release leaves a tag whose action cannot run.
changed the title [-]v6.3.0 GitHub Action fails: Docker image asyncapi/github-action-for-cli:6.3.0 not found on Docker Hub[/-][+][BUG] asyncapi/cli@v6.3.0 action fails: Docker image asyncapi/github-action-for-cli:6.3.0 not found[/+]on Nov 10, 2026
Activity
github-actions commentedon Nov 10, 2026
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
CasaSky commentedon Nov 10, 2026
Additional findings:
asyncapi/cli:6.3.0is on Docker Hub. Only the action imageasyncapi/github-action-for-cli:6.3.0(used byaction.yml) is missing.Release Docker Imagerun forv6.3.0ended as cancelled after 6h: https://github.com/asyncapi/cli/actions/runs/42328838823. The workflow publishesasyncapi/clifirst and the action image (./github-action/Dockerfile) afterwards, so it looks like the first image was pushed and the second was never built. Thev6.2.3run succeeded in ~32 min.asyncapi/cli@v6.3.0for everyone.Question: why are there two separate Docker Hub repositories (
asyncapi/cliandasyncapi/github-action-for-cli), and why does the action use the separate wrapper image rather thanasyncapi/cli? Having a second image to publish makes releases like this one fragile, since a partially failed release leaves a tag whose action cannot run.[-]v6.3.0 GitHub Action fails: Docker image asyncapi/github-action-for-cli:6.3.0 not found on Docker Hub[/-][+][BUG] asyncapi/cli@v6.3.0 action fails: Docker image asyncapi/github-action-for-cli:6.3.0 not found[/+]Shurtu-gal commentedon Nov 10, 2026
I will look into this in the coming weekend.