Repository navigation
Conversation
The HA Supervisor detects app updates by comparing the version string in the app config against the installed version; images are published under exactly that version as their tag. A device-visible change without a bump therefore ships to nobody (existing installs never see it) and silently repoints an already-published version tag, so 'the same version' means different images depending on install time (the opposite of immutable releases). Add a repo-agnostic version-guard workflow: fails pull requests and pushes to main when device-visible app files (rootfs, Dockerfile, config.yaml, apparmor.txt, translations) changed without a version bump. App discovery by config-file presence, plain git for the diff and version compare, fail-open where a guard cannot know better (new apps, no-base pushes). Docs-only changes pass untouched. Assisted-by: Goose:glm-5.3-flash
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 HA Supervisor detects app updates by comparing the version string in the app config against the installed version; images are published under exactly that version as their tag. A device-visible change without a bump therefore ships to nobody (existing installs never see it) and silently repoints an already-published version tag, so "the same version" means different images depending on install time (the opposite of immutable releases).
So while the Supervisor does not enforce its own update model (arguably a design flaw), we can at least protect against violating it by accident (or ignorance) downstream.
Hence add a repo-agnostic version-guard workflow: fails pull requests and pushes to
mainwhen device-visible app files (rootfs/,Dockerfile,config.yaml,apparmor.txt,translations/) changed without a version bump. App discovery by config-file presence, plain Git for the diff and version compare, fail-open where a guard cannot know better (new apps, no-base pushes). Docs-only changes pass untouched.Assisted-by: Goose:glm-5.3-flash