Hi store team,
I’d like to request a track creation grant for the home-assistant snap
(publisher: giaever-online), so that new version tracks can be created
self-served as upstream releases arrive.
Snap: home-assistant (unrelated, but same tracking as the home-assistant-snap)
Publisher: giaever-online (Giaever.online)
Requested track naming pattern: YYYY.M — matching upstream Home
Assistant Core release versions (e.g. 2026.7, 2026.8, 2026.9, …).
Cadence: monthly — Home Assistant Core publishes a new minor release the
first Wednesday of every month, and each release line receives patch updates
for roughly a month after. Per-version tracks let users pin to a release line
and control when they take the (occasionally breaking) monthly upgrade,
while latest continues to follow the newest release.
Precedent: this mirrors the track scheme already in production use on my
existing home-assistant-snap (same publisher), which carries granted tracks
2025.7, 2025.8, 2025.9, 2025.10, 2025.11, etc. The home-assistant
snap is its successor (container-based architecture for Ubuntu Core), and
will follow the identical track lifecycle.
Commitment: tracks will only ever be created following the YYYY.M
pattern above, one per upstream release; no other track names will be
created under this grant.
Given the fixed monthly cadence, a standing grant would avoid a recurring forum request every month. Happy to provide any further detail.
Thanks!