Skip to content

feat(hacs): distribute via taskmate.zip release asset#581

Merged
tempus2016 merged 1 commit into
mainfrom
chore/hacs-zip-release-flip
Jun 23, 2026
Merged

feat(hacs): distribute via taskmate.zip release asset#581
tempus2016 merged 1 commit into
mainfrom
chore/hacs-zip-release-flip

Conversation

@tempus2016

Copy link
Copy Markdown
Owner

Flips hacs.json to "zip_release": true + "filename": "taskmate.zip".

Now that v4.3.1 (latest release) carries a taskmate.zip asset, HACS will install via the asset and surface its download_count — the download counter starts moving instead of being stuck at 0.

This is deliberately a separate PR after the v4.3.1 release: HACS reads hacs.json from the default branch and zip_release governs install of every version, so flipping it before a live release had the asset would have broken installs for everyone. The latest release now has the asset, so there is no breakage window.

Verified the published v4.3.1 asset: manifest.json at zip root, version 4.3.1, www/ + translations/ + brand/ present, no __pycache__/.pyc, zip integrity OK.

Now that v4.3.1 (latest) carries a taskmate.zip asset, switch HACS to
zip_release so installs pull the asset and HACS surfaces its download_count.
Safe to flip only after a live release has the asset — earlier would have
broken installs (HACS reads hacs.json from the default branch and would
request a non-existent asset on the latest release).
@tempus2016 tempus2016 merged commit 2472530 into main Jun 23, 2026
10 checks passed
@tempus2016 tempus2016 deleted the chore/hacs-zip-release-flip branch June 23, 2026 23:25
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