Conversation
The legacy add-on config has pointed at image tag 0.1.74 since it was introduced, but that tag was never published to ghcr.io - only 0.1.80 and 0.1.81 exist. Installing the legacy add-on from the store fails with "[404] manifest unknown". Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Installing Pipecat Assist Legacy amd64 from this repo's add-on store fails:
addons/pipecat_assist_legacy_amd64/config.yamlhas pinnedversion: "0.1.74"since the legacy variant was introduced in v0.1.76, but that image tag was never published — ghcr only has0.1.80and0.1.81.Fix
Bump the legacy add-on config to
0.1.81(verified working: pulled and booted cleanly on a pre-x86-64-v2 Core 2 Duo host, Pipecat 1.4.0 starts with no NumPyX86_V2error).Root cause worth fixing too
The release process bumps only
addons/pipecat_assist/config.yaml, so the legacy config will drift again on the next release (v0.1.80 and v0.1.81 tags both still carry0.1.74for legacy). Including the legacy config in the release version-bump step would prevent a repeat.🤖 Generated with Claude Code