Repository navigation
ci: publish native beta pins automatically after green checks - #24
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
New native FTW betas currently create a Home Assistant pin PR that needs a manual merge. The pin workflow now verifies the bot PR, waits for all seven Check jobs on its exact commit, and merges it automatically. That makes each published beta available through Supervisor without another manual step.
Publication accepts only a same-repository bot PR to main whose three pin files exactly match a change regenerated from the public native receipt and checksum files. It refuses extra edits, stale heads, downgrades and failed or skipped checks. If main moves, it updates the branch and tests again. It explicitly starts Check on main after merging because GITHUB_TOKEN merges do not trigger push workflows.
Validation: 180 offline tests pass, including real git diff fixtures for valid pins and tampered Dockerfile/config/changelog, plus missing/failed/skipped jobs, wrong commits, caller checks and merge SHA matching. Repository validation and Python compilation pass. GitHub CI also builds and smoke-tests both architectures.
This publishes updates to the HA store. Each user's Supervisor Auto update setting still controls installation.