Add-on fails to install — config.yaml points to ghcr.io/marcinnowak79/gemini-live-proxy-amd64:1.1.0, but checking the package page (https://github.com/marcinnowak79/gemini-live-proxy/pkgs/container/gemini-live-proxy-amd64), the latest published tag is 1.0.22. 1.1.0 doesn't exist in the registry.
Supervisor log:
Failed to fetch manifest for ghcr.io/marcinnowak79/gemini-live-proxy-amd64:1.1.0 - 404
Can't install ghcr.io/marcinnowak79/gemini-live-proxy-amd64:1.1.0: [404] manifest unknown
Quick fix: either push the 1.1.0 image or bump config.yaml back to 1.0.22.
Longer term — happy to submit a PR adding a GitHub Actions workflow that builds and pushes the image to GHCR automatically on tagged releases, so this class of version/image mismatch can't happen again. Let me know if that'd be welcome before I put time into it.
Add-on fails to install — config.yaml points to ghcr.io/marcinnowak79/gemini-live-proxy-amd64:1.1.0, but checking the package page (https://github.com/marcinnowak79/gemini-live-proxy/pkgs/container/gemini-live-proxy-amd64), the latest published tag is 1.0.22. 1.1.0 doesn't exist in the registry.
Supervisor log:
Quick fix: either push the 1.1.0 image or bump config.yaml back to 1.0.22.
Longer term — happy to submit a PR adding a GitHub Actions workflow that builds and pushes the image to GHCR automatically on tagged releases, so this class of version/image mismatch can't happen again. Let me know if that'd be welcome before I put time into it.