Repository navigation
Conversation
native-release.yml now refuses to publish a beta unless the job "site full" of site.yml succeeded on the source commit: every scenario of go/test/site against device-simulator, with known failures still failing. A dry run warns instead. Stable promotes a tested beta and is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The rig no longer runs in GitHub Actions (Fredrik, 22 Oct). A runner on its own machine posts the commit status siterig/full after a full run of a commit, and the beta gate reads that status: the latest siterig/full on the source commit must be success. The step reads; it never runs the rig. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
frahlg
changed the title
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
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.
Proposal, changes the release flow: needs Fredrik's approval. Merge after #1797, which adds the site test and the runner that posts
siterig/full.Problem
The beta's simulator test on 21 October was run by hand, from a folder outside the repo. Nothing stops a beta whose Core has not met the simulated house.
Proposal
native-release.yml, channelbeta, gets one step right after "Bind the candidate to its source". It reads the commit statuses of the exact source commit and publishes only if the latestsiterig/fullissuccess. The step only reads; it never runs the rig.siterig/fullcomes fromsiterig-runner(go/test/site/runnerin #1797), which runs on a machine of its own, not in GitHub Actions. It runs the full set on each newmastercommit and posts the status on that SHA: success when every scenario passed and every known failure still failed as known.statuses: read.What it costs the release
The beta commit is the merge of the Version Packages PR. The runner picks it up within its polling interval (5 min) once it lands on
master. The full set took 72 minutes in three lanes on an M5 MacBook on 22 October;s12-20alone takes 56, so more lanes would not shorten it. The owner dispatches the beta aftersiterig/fullturns green on that commit; until then the gate refuses with the commit and the state it found.Alternatives considered
go/,web/and driver pin. Saves the wait after Version Packages, which only changespackage.jsonand the changelog, but a tree rule is easier to get wrong than "this commit passed".Tests
python3 -m unittest discover -s scripts -p 'test_write_native_release_notes.py',test_ha_addon_dispatch.py,test_check_native_release_order.pyand.github/scripts/test_discord_release.pypass. The step itself runs only on a dispatch of the release workflow.🤖 Generated with Claude Code