Skip to content

fix(image-update): leave an app built on this box out of the update check - #12

Merged
inkly merged 1 commit into
mainfrom
fix/image-check-skips-built-apps
Sep 27, 2026
Merged

inkly merged 1 commit into
mainfrom
fix/image-check-skips-built-apps

Conversation

@inkly

@inkly inkly commented Sep 27, 2026

Copy link
Copy Markdown
Collaborator

An app whose every service is built on the box (build: sections, as a git app) runs no image a registry publishes. The check of every app still listed it as unchecked, so after each check the dashboard reported "Could not check jarvis (this app runs no image with a tag to compare). They keep their previous state.", which reads as a failure every time.

CheckImageUpdates now leaves such an app out, the same way pulledServiceNames already leaves out the built services of an app that also pulls images. An app that pulls even one image is still checked on it. The single-app check keeps answering why, with the reason reworded to "none of its services runs an image a registry publishes".

Test: TestAnAppBuiltHereIsLeftOutOfTheCheck.

…heck

An app whose every service has a build: section, a git app or a compose file
built here, runs nothing a registry publishes. The check of every app listed it
among the apps it could not check, and the dashboard said so after every check:
"Could not check jarvis (this app runs no image with a tag to compare). They keep
their previous state." It is not a failure, and the check now leaves such an app
out, as it already left out the built services of an app that pulls others. The
single-app check still answers why, in plainer words.
@inkly
inkly merged commit b073da7 into main Sep 27, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant