Repository navigation
chore(release): 2.0.0b17 version bump, release notes, and README/roadmap refresh - #855
Merged
GreenGrassBlueOcean merged 1 commit intoNov 3, 2026
Merged
Conversation
GreenGrassBlueOcean
merged commit Nov 3, 2026
eb3457e
into
v2-phase1-architecture
16 of 17 checks passed
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
What is the problem
Before tagging the
2.0.0b17pre-release, the version must be aligned acrossconst.py,manifest.json, the Lovelace bus monitor card, and the install/upgrade docs, and the release notes must capture everything merged across the 61 pull requests since2.0.0b16.What is the solution
2.0.0b17in:custom_components/myhome/const.pycustom_components/myhome/manifest.json(pinsOWNd==2.0.0b13)custom_components/myhome/frontend/myhome-bus-card.jsdocs/getting-started/installation.mddocs/migration/upgrade-from-094.mdREADME.md,ROADMAP.md,docs/roadmap.md, anddocs/roadmap/beta-differences.mdto2.0.0b17with detailed delta logs and delivery timelines..github/release-notes/2.0.0b17.md, the GitHub release body covering all 61 pull requests merged since2.0.0b16:calibrate_coverstores the F411 120 s cutoff (M=1) as a travel time #837, fix(cover): refuse every configurator run-time limit in calibrate_cover, not only 60 s (#837) #843, fix(cover): settle a full run at the actuator's own stop up to 0.5 s before the travel time (#770 end-stop follow-up) #847): timed covers settle on travel time + 2 s from known positions; actuator stop within 0.5 s before stored travel time is recognized as limit stop; configurablemin_position_delta(1–5 %, default 2 %); translated stops (*2*1000#0*WHERE##) stop timed runs; and calibration guards against minute-boundary configurator limits.audio_field_report.yml,bug_report.yml,device_request.yml) to reference2.0.0b17.scripts/backfill_beta_docs.pywith2.0.0b16historical milestone tag.State Diagram
flowchart LR A["Bump version in const.py, manifest.json, bus card & docs"] --> B["Draft release notes for 61 PRs since b16"] B --> C["CI & package_release.py green (5,324 tests, 100% cov)"] C --> D["Merge release PR into v2-phase1-architecture"] D --> E["Tag 2.0.0b17 & publish GitHub Pre-Release with myhome.zip"]Hardware Verification
All subsystem changes in
2.0.0b17are verified on live plant hardware and captured traces:How is it tested
scripts/verify_ha_standards.py: Platinum 54/54 rules satisfied, PARALLEL_UPDATES = 0 across 11 platforms, 0 ruff errors.scripts/sync_documentation.py --check: Clean calibration (0 errors, 0 broken links).scripts/package_release.py --tag 2.0.0b17: Verified HACS-compliant archivemyhome.zip(740,278 bytes, 90 files).Where are the traces
tests/fixtures/traces/discussion_819/myhome_trace_3550_central_unit_live.jsontests/fixtures/traces/discussion_818/myhome_trace_HL4684_tuner_live.jsontests/fixtures/traces/f461_live_2026-10-18/tests/fixtures/traces/f461_who14_live_2026-10-18/tests/fixtures/traces/issue_466/config_entry-myhome_F454_step_commands.jsontests/fixtures/traces/issue_667/myhome_trace_F461_impulse_intercom_2026-10-19.jsontests/golden/firmware_oracle.json(6,500 verdicts)What does the Firmware Oracle / Encyclopedia say
manifest.jsonpinsOWNd==2.0.0b13. Gateway profiles, frame syntax, and dimension parsers are strictly verified against the OpenWebNet Encyclopedia Machine KB and Firmware Oracle.Checklist
2.0.0b16merged intov2-phase1-architectureOWNd==2.0.0b13is published on PyPImyhome.zipverified