fix(updates): thread catalog repoURL into the live check so the GitHub Releases tier fires - #74
Merged
Conversation
…b Releases tier fires The GitHub Releases tier (resolveViaReleases) was dead on the live /api/updates path: handleUpdates built each InstalledImage without a repoURL, so the tier bailed on its first line and images that couldn't be resolved by tag or digest fell through to "version unknown" — even when the app has a github.com source in the catalog. Enrich each image server-side by matching it to its catalog app's repoURL via the new reusable repoURLForImage() (reuses imageRepoPath/repoPathsMatch). The tier runs last, so this only converts former unknowns into version answers and can't change an existing registry/digest verdict. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
tyrelchambers
marked this pull request as ready for review
July 20, 2026 20:46
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.
The GitHub Releases tier (resolveViaReleases) was dead on the live /api/updates
path: handleUpdates built each InstalledImage without a repoURL, so the tier
bailed on its first line and images that couldn't be resolved by tag or digest
fell through to "version unknown" — even when the app has a github.com source in
the catalog.
Enrich each image server-side by matching it to its catalog app's repoURL via
the new reusable repoURLForImage() (reuses imageRepoPath/repoPathsMatch). The
tier runs last, so this only converts former unknowns into version answers and
can't change an existing registry/digest verdict.
Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com