Repository navigation
chore(release): 2.0.0b16 version bump, release notes, and README/roadmap refresh - #703
Merged
GreenGrassBlueOcean merged 5 commits intoOct 21, 2026
Merged
Conversation
GreenGrassBlueOcean
marked this pull request as draft
October 13, 2026 11:19
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
GreenGrassBlueOcean
force-pushed
the
chore/release-2.0.0b16
branch
2 times, most recently
from
October 19, 2026 12:38
5348ac3 to
c978d07
Compare
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- Count and summarize every pull request merged since 2.0.0b15, grouped by subsystem, with the expose engine (#750), slat tilt (#508) and impulse covers (#667) as the headline features. - Covers: the start-up floor is the per-cover min_motor_pulse (#708), timed runs end at the stop status (#707) and full-travel keypad runs report the end (#760); drop the "lift only" and open follow-up lines, both shipped. - New behaviour-change section: sync_time refuses half-hour time zones (#764) and advanced: true on an F411 now warns (#762). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GreenGrassBlueOcean
force-pushed
the
chore/release-2.0.0b16
branch
from
October 21, 2026 18:17
c978d07 to
b0e2aac
Compare
The README, ROADMAP.md, docs/roadmap.md and docs/roadmap/beta-differences.md still named v2.0.0b14 as the latest release; the b15 release never updated them. - README: install commands, download link and status line point to 2.0.0b16. - ROADMAP.md: current release b16 (OWNd 2.0.0b11), a "Delivered in b14 - b16" gantt section, and rows for the expose engine and the cover work. - docs/roadmap.md: the "Merged after b14" section is the b15 release, a b16 section is added, and the slat tilt bar is done (#508), no longer open. - beta-differences: b15 and b16 columns and entries, a cover positioning and an expose row; the b14 OWNd cell is 2.0.0b9 (was 2.0.0b8). The b14 entry gets its release date and tag compare, and its cover start-up floor bullet moves to b16, where #702 shipped. - backfill_beta_docs.py: add the released 2.0.0b14 and 2.0.0b15 to the milestone list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GreenGrassBlueOcean
marked this pull request as ready for review
October 21, 2026 18:42
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.0b16pre-release, the version has to be the same inconst.py,manifest.json, the Lovelace bus monitor card and the install/upgrade docs, and the release notes have to cover what merged since2.0.0b15.How is it solved
2.0.0b16incustom_components/myhome/const.py,custom_components/myhome/manifest.json,custom_components/myhome/frontend/myhome-bus-card.js,docs/getting-started/installation.mdanddocs/migration/upgrade-from-094.md(same set as chore(release): depend on OWNd 2.0.0b10 and drop temporary WHO 4 sign helper #571 forb15).README.md,ROADMAP.md,docs/roadmap.mdanddocs/roadmap/beta-differences.mdto2.0.0b16(dc3b2c60)..github/release-notes/2.0.0b16.md, the GitHub release body covering all 83 pull requests merged since2.0.0b15:min_motor_pulse(timed, feat(cover): per-cover motor start-up floor instead of single constant (#704) #708); no widening while an advanced cover moves; timed runs end at the actuator's stop status (fix(cover): end timed runs on stop status instead of stop write (#705) #707) and full-travel keypad runs report the end (fix(cover): confirm end_stop on full-travel bus runs and scope run timeouts #760).myhome.sync_timerefuses half-hour time zones (fix(services): reject half-hour time zones in sync_time with a translated error #764);advanced: trueon a standard F411 logs a warning (fix(cover,docs): warn and guide when F411 standard shutters set advanced: true (#761) #762).myhome.yamlsettings copied into the config entry (feat(discovery): reusable sweep poll gate, dimmer capability probe, and legacy YAML migration (#733) #742), the HA 2026.11 name migration (fix(migrate): preserve legacy entity friendly_name as compat_name on HA 2026.11+ #727), and the test/CI work.Pre-merge checklist
2.0.0b15(83 as of test(oracle): read empty-bus NACKs on F460/F461/MyHomeServer1 by verdict #766)OWNd==2.0.0b11is published on PyPI (CI installs the wheel from there)v2-phase1-architecture; 83 PRs total)v2-phase1-architecture(all 17 CI checks green &myhome.ziprelease package verified)Post-merge release step (after merging into
v2-phase1-architecture)2.0.0b16GitHub Pre-Release targetingv2-phase1-architecture, paste.github/release-notes/2.0.0b16.mdas the release body, and attachmyhome.zip.How is it tested
ruff,mypy,scripts/verify_ha_standards.py,scripts/sync_documentation.py --checkandscripts/package_release.py --tag v2.0.0b16pass.docs/configuration/covers.mdon the base.State Diagram
flowchart LR A["Bump version in const.py, manifest.json, bus card & docs"] --> B["Release notes for the 83 PRs since b15"] B --> C["CI & package_release.py green (17/17)"] C --> D["Merge PR #703 into v2-phase1-architecture"] D --> E["Tag 2.0.0b16 & publish GitHub Pre-Release with myhome.zip"]Where are the traces
The cover and plant changes in the notes are grounded in:
tests/fixtures/traces/issue_466/config_entry-myhome_F454_step_commands.json(F454 step commands on Somfy Ilmo 50 WT motors)tests/fixtures/traces/f461_live_2026-10-18/myhome_trace_F461_live_2026-10-18.json(physical F461 2.0.11)tests/fixtures/traces/f461_who14_live_2026-10-18/myhome_trace_F461_who14_live_2026-10-18.json(physical F461 2.0.11, WHO 13/14)tests/fixtures/traces/issue_667/myhome_trace_F461_impulse_intercom_2026-10-19.json(physical F461 impulse relay and intercom, feat(cover,lock): impulse garage/gate control, multi-factor safety approval, and intercom events #667)tests/golden/firmware_oracle.json(6,500 firmware oracle verdicts, 12 emulated gateways)What does the Oracle / Encyclopedia say
manifest.jsonpinsOWNd==2.0.0b11. Its gateway profiles are checked againsttests/golden/firmware_oracle.jsonin CI (#743, #745), and on F460 / F461 / MyHomeServer1 the conformance tests read the oracle's verdict rather than its empty-bus replies (#766).🤖 Generated with Claude Code