Repository navigation
ci(ownd-smoke): make the OWNd "latest" target non-blocking - #644
Closed
GreenGrassBlueOcean wants to merge 1 commit into
Closed
GreenGrassBlueOcean wants to merge 1 commit into
GreenGrassBlueOcean wants to merge 1 commit into
Conversation
"pinned" tests the OWNd version the manifest ships and stays a hard gate. "latest" (PyPI head) is an early-warning canary for upstream drift, so a failure there should not block PRs that depend on an unreleased OWNd. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.
Summary
In
ownd-smoke.yml,latestwasallow-failure: false, so it blocked PRs the same waypinneddoes. This sets it toallow-failure: true, likedev.pinnedtests the OWNd versionmanifest.jsonships. It stays a hard gate, because a failure means we would ship code that breaks against the dependency we declare.latesttests PyPI head. It is not what users get from the manifest and the PR author doesn't control it. It is an early-warning canary for upstream drift, so it shouldn't block merges. Today it is redundant withpinned(both resolve to 2.0.0b9). It would start blocking PRs on its own when OWNd publishes something incompatible, or when a PR such as fix(climate): align central unit mode commands and fan mode with OWNd canonical protocol (OWNd#77) #630 depends on an OWNd release that is not out yet.devis unchanged (already non-blocking).Notes
continue-on-erroronly turns the job green. IfOWNd (latest / Py3.14)is also a required status check in branch protection forv2-phase1-architecture, it has to be removed there too (Settings → Branches). That is a repo setting and this PR does not touch it.HA Compatibility,test-coverage,Run Pytest Suite & Coverage,OWNd (pinned)). Those stay red until the OWNd 2.0.0b10 bump lands, as described in that PR.🤖 Generated with Claude Code