Please use fewer releases

[sandymac]

What problem does this solve?

One update per day is healthy, maybe two if you quickly catch an opps.

Proposed solution

Accumulate a days worth of changes between releases.

Alternatives considered

Consider a stable and testing release system as an alternative to continuous releases.

[LayerTM]

Thank you — the count is real and worth answering plainly: this add-on published six releases today (1.59.0 through 1.59.5). With auto-update enabled that is six restarts of your Home Assistant in one day, which is more than any user should absorb for changes that could have travelled together.

Most of those were separate fixes that each proved out on their own, and shipping each one the moment it was ready optimised for our side of the process rather than for the person running it.

We are deciding now between batching a day's changes into one release, and splitting the repository into a stable channel plus a testing channel for anyone who wants the fixes early. We will reply here with the decision rather than let it quietly change — and either way, the day of six updates is not repeating.

[LayerTM]

Decision, as promised: one release per day.

Changes will accumulate on the main branch and be cut as a single release with a single changelog entry, instead of a tag per fix. The only exception is a fix for something actively breaking people's installations, which still goes out immediately and will say so in its entry.

We are not adding a separate testing channel for now. It would give early access to anyone who wants it, but it doubles what has to be verified before anything reaches a stable user, and that verification is what makes the daily release worth trusting. If enough people ask for the early channel, we will revisit it here.

The mechanism is moving into the release process itself rather than being left to discipline, so the cadence holds whether or not anyone remembers it.

Thank you for saying it plainly — six updates in a day was a real cost you were paying for our convenience.

[LayerTM]

Update: this is now in place.

Releases are no longer cut on every push to main. A scheduled job runs once a day (12:00 UTC), checks whether the version on main has a release yet, and only then re-runs every CI gate for that commit and cuts the release. Several version bumps landing in one day now arrive as a single release, and its notes carry every changelog section since the last one, so nothing is lost in the bundling.

There is one deliberate exception: a fix that is actively breaking installs can be released by hand without waiting for the clock — it goes through the same gates.

First release under the new cadence: v1.59.6, cut today by the mechanism rather than by a push.

Thanks for the report — the six releases in a day you counted were real, and this is the fix.

[LayerTM]

Closing this out: the daily cadence has held since v1.59.6 (2026-09-19) — one release a day, each entry stating plainly when it's the stated exception for something actively broken. Thanks again for the report.

[LayerTM]

Correction to my closing comment: on 2026-09-24 two releases went out (v1.59.7 and v1.59.8), and the second one's changelog entry did not call out an exception. Since then it has been at most one release a day. The issue stays closed — reopen it if the cadence slips again.

[sandymac]

Appreciate the current balance in cadence and progress. Keep it up! thx

[LayerTM]

Thanks for the feedback!