Describe the bug
The Docker image ghcr.io/erebe/wstunnel:v10.5.5 is missing from the GitHub Container Registry, even though the v10.5.5 GitHub release was published on 2026-05-05. The latest available image is v10.5.4.
To Reproduce
Query the GHCR tags list (no authentication required):
TOKEN=$(curl -s 'https://ghcr.io/token?service=ghcr.io&scope=repository:erebe/wstunnel:pull' \
| python3 -c 'import sys,json; print(json.load(sys.stdin)["token"])')
curl -s -H "Authorization: Bearer $TOKEN" \
'https://ghcr.io/v2/erebe/wstunnel/tags/list' \
| python3 -c 'import sys,json; tags=json.load(sys.stdin)["tags"]; print(tags[-5:])'
# ['v10.5.0', 'v10.5.1', 'v10.5.2', 'v10.5.3', 'v10.5.4']
Or check the manifest directly — it returns 404:
curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $TOKEN" \
'https://ghcr.io/v2/erebe/wstunnel/manifests/v10.5.5'
# 404
Expected behavior
ghcr.io/erebe/wstunnel:v10.5.5 (and latest) should be available after each release, as was the case for all previous versions.
Your wstunnel setup
N/A — the issue is with the published Docker image, not a running instance.
Desktop (please complete the following information)
- OS: Linux
- Version: v10.5.5
Additional context
The release workflow (.github/workflows/release.yaml) only builds binaries via GoReleaser — there is no Docker build/push step. Images appear to have been published manually up to v10.5.4. Adding automation for this would prevent the issue from recurring.
Describe the bug
The Docker image
ghcr.io/erebe/wstunnel:v10.5.5is missing from the GitHub Container Registry, even though the v10.5.5 GitHub release was published on 2026-05-05. The latest available image isv10.5.4.To Reproduce
Query the GHCR tags list (no authentication required):
Expected behavior
ghcr.io/erebe/wstunnel:v10.5.5 (and latest) should be available after each release, as was the case for all previous versions.
Your wstunnel setup
N/A — the issue is with the published Docker image, not a running instance.
Desktop (please complete the following information)
Additional context
The release workflow (.github/workflows/release.yaml) only builds binaries via GoReleaser — there is no Docker build/push step. Images appear to have been published manually up to v10.5.4. Adding automation for this would prevent the issue from recurring.