Skip to content

Frozen v0.3.1 reference — corrected submission continues in v0.3.2 - #1470

Draft
JohanBendz wants to merge 238 commits into
modernize-2026from
modernize-2026-issues
Draft

JohanBendz wants to merge 238 commits into
modernize-2026from
modernize-2026-issues

Conversation

@JohanBendz

@JohanBendz JohanBendz commented Sep 27, 2026 •

Copy link
Copy Markdown
Owner

Corrected submission candidate: v0.3.2

The maintainer requested publication-copy corrections on 2026-10-04. Draft release PR #1514, branch release-0.3.2, is now the intended 0.3.x Live submission candidate. It preserves this frozen 0.3.1 runtime and changes only publication text, version metadata, packaging exclusions and maintenance guidance. This PR is retained as the unmerged frozen 0.3.1 reference; do not promote it in parallel or mix in 0.4 work. Actual Live remains 0.2.76 and Test remains 0.3.1 until a real Athom submission/promotion. Confirm 0.3.2 Live before 0.4.0 Test.


Release v0.3.1 — published to Test (2026-10-01)

Status: Test published (confirmed by maintainer) · 0.2.76 remains Live · PR Draft / unmerged while field acceptance is collected. Code is frozen at 7583b4bb2fa91600c2301eb142335312a6a7cac4. Base modernize-2026 is the previous 0.3.0 Test baseline, not the current Live/default branch (SDK3).

Review snapshot: 238 commits / 207 changed files versus modernize-2026, with no file deletions. GitHub reports the PR mergeable, without conflicts, and the head has a successful CI275 at this exact SHA: clean install, Homey Compose, committed generated manifest/index, repository/regression tests, Homey publish validation and whitespace. No submitted GitHub PR reviews at this checkpoint. CI establishes technical/repository validity, not physical acceptance of every Zigbee variant.

Scope and release safety

Decision gate

Keep this PR Draft and the 0.3.1 head unchanged while Test evidence arrives. Review release-specific reports and actual Homey device behavior, then explicitly decide on Ready for Review/merge and a separate Live publication when support and recovery capacity are available. Monday 2026-10-05 is the earliest planned review point, not an automatic promotion date. A GitHub merge alone does not publish an Athom Live release. Avoid retargeting this release PR to legacy default SDK3; plan any eventual modernize-2026 → main transition separately.


Original adoption / triage ledger

Base: modernize-2026
Work branch: modernize-2026-issues

Historical note: implementation was frozen at CI275 for the 0.3.1 Test publication. Subsequent 0.4.0 development is separately tracked in #1469. Historical PR cleanup is complete: all external PRs have been reviewed, selectively reimplemented, closed as superseded, or converted into focused current issues. The only open PR left in the repository is this draft.

Adopted / reimplemented

Generated app.json and SUPPORTED_DEVICES.md are synchronized with the Compose sources.

Deliberately not absorbed / canonical follow-up

Review hygiene

Validation and release role — 2026-09-30

This PR is now the frozen 0.3.1 development/Test follow-up to the 0.3.0 modernization baseline.

Current release model:

  • Live: SDK3 — 0.2.76
  • Test: modernize-2026 — 0.3.0
  • Development: modernize-2026-issues — 0.3.1 (this PR)

Validation checkpoint for this PR:

  • HEAD 725d7b2
  • 236 commits ahead, 0 behind modernize-2026
  • CI273 fully green
  • 92/92 repository tests passing
  • Homey Compose/build green
  • committed generated app.json matches Compose
  • generated SUPPORTED_DEVICES.md current
  • Homey publish validation green
  • whitespace check green

The branch has also been tested locally on Homey and appears functionally as stable as 0.3.0, while adding the larger verified issue/device backlog.

Freeze

This PR intentionally remains draft and frozen while 0.3.0 receives Homey Test feedback.

Do not add further backlog work to this branch during the freeze.

Planned release sequence:

  1. Verify 0.3.0 stability in Test.
  2. Promote 0.3.0 to Live.
  3. Publish 0.3.1 as Test.
  4. Keep 0.3.1 frozen during its Test cycle.
  5. Create the next development branch from this line, provisionally develop-0.4, and resume new development there.

Physical validation of the 0.3.1-specific changes remains tracked in #1469, including FingerBot #869 and the other retained hardware-retest items.

The old temporary 0.2.77 release-candidate plan is retired; 0.2.77 was never the intended App Store milestone in the final release sequence.

@JohanBendz JohanBendz mentioned this pull request Sep 27, 2026

Copy link
Copy Markdown
Owner Author

Maintainer release-status signal — 2026-10-02

Reported 0.3.1 Test adoption exceeds 2,600 installations, with no crashes or errors reported as of this update. This is reported operational feedback rather than a guarantee that every physical device has been tested. The source branch and this PR remain frozen at 7583b4bb2fa91600c2301eb142335312a6a7cac4; no merge, branch update, Homey submission or Live promotion was performed.

Next development objective is 0.4.0 Test around 6–7 October 2026. Please explicitly review the 0.3.1 Live-promotion / occupied Test-channel decision before issuing the next Test release, so this well-exercised candidate is not silently superseded. The separate 0.4 Test-readiness plan now pins the full 0.3.1 compatibility baseline and protects sensitive legacy light source against unapproved changes. This PR remains Draft until a deliberate release decision.

Copy link
Copy Markdown
Owner Author

Maintainer release-sequence decision — 2026-10-04

Confirmed deployment order (hard dependency):

  1. Current Live remains v0.2.76 while current Test v0.3.1 is finally reviewed; do not claim a promotion has happened.
  2. FIRST promote exactly the existing tested v0.3.1 build to Live, using frozen branch modernize-2026-issues HEAD 7583b4bb2fa91600c2301eb142335312a6a7cac4. Complete 0.3.1 Test feedback and targeted release-safety review, check core existing device upgrades/flows, then submit for Athom certification and manually publish to Live once approved. This is the v0.2.76 → v0.3.1 Live step. Draft #1470 is the matching GitHub release lane; GitHub merge alone is NOT Homey publication, and do not redirect it into develop-0.4 or archived SDK3.
  3. ONLY AFTER v0.3.1 is confirmed actually available in Live, complete the separate develop-0.4 final-SHA/pairing-assets/preflight sign-off and submit v0.4.0 to public Test, replacing v0.3.1 Test. Physical trials of 33 new 0.4 exact manufacturer/model rows are explicitly expected INSIDE public Test, not an artificial gate before Test publication.
  4. No implicit permission to publish or merge was given by recording this release order. The app-version numbers must remain monotonic; if v0.4.0 Test later fails, submit higher-version corrective build such as v0.4.1 rather than expect republishing v0.3.1 to downgrade Test installs.

This updates the previously open Test-channel decision in docs/0.4.0_RELEASE_PREFLIGHT.md / tracker #1469: choose the v0.3.1-Live-first path. All code, manifests, PR state and Homey channel publication remain untouched by this coordination note. Athom documentation: https://apps.developer.homey.app/app-store/publishing and https://apps.developer.homey.app/app-store/updates .

Copy link
Copy Markdown
Owner Author

Frozen 0.3.1 Live-candidate review — 2026-10-04

Review evidence and remaining checks now committed via merged #1513. Exact release source is still 7583b4bb2fa91600c2301eb142335312a6a7cac4, unchanged; this PR remains OPEN/DRAFT/unmerged. CI275 remains SUCCESS; unchanged local source passed 95/95 tests. Structural audit against actual 0.2.76 SDK3 source found no removed driver, capability, setting or Flow-card IDs. The retained siren-volume action has corrected labels with unchanged numeric argument IDs.

Reviewed 650 GitHub conversation comments updated since September 30 and targeted existing-device issues. No new evidence in that retrieved feedback set establishes a 0.3.1 app crash or broad upgrade regression. Current-version physical confirmation is still missing for several targeted cases, including TH05Z battery, FingerBot and remote gestures. Forum/private diagnostics/current Athom telemetry were unavailable; do not describe this as exhaustive physical acceptance. DP36 thermostat logging remains a known 0.3.0/0.3.1 observation, with mitigation only in 0.4.

The release documents now pin 0.3.1 Live BEFORE 0.4.0 Test. develop-0.4 is the feature-frozen 0.4.0 stabilization lane, and develop-0.4.1 exists for new development from validated checkpoint 210ac20. No new code is justified in this frozen 0.3.1 candidate by the reviewed evidence. Complete final operational sign-off and actual Athom Live promotion using the existing tested build before replacing Test. No Homey publication or release-PR merge performed by this review.

@JohanBendz JohanBendz changed the title Release v0.3.1 (Test): modernization and verified backlog fixes Frozen v0.3.1 reference — corrected submission continues in v0.3.2 Oct 4, 2026

Copy link
Copy Markdown
Owner Author

Post-Live hotfix note: #1517 exposed a regression in curtain_module_2_gang introduced when Flow action listeners were moved to driver level. The driver accidentally became Homey.Driver despite declaring Zigbee subdevice secondModule.

release-0.3.3 restores ZigBeeDriver while preserving the Flow routing fix and adds regression coverage. The runtime fix/test are also forward-ported to develop-0.4 and develop-0.4.1. Validation is tracked in #1518.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant