Ship spotcast.zip as a release asset for HACS - #79
Merged
Merged
Conversation
HACS now installs from a spotcast.zip attached to each release (zip_release) instead of the auto-generated source archive. The zip holds only the integration, and GitHub counts its downloads per release, which gives a real install/update count. A new workflow builds the zip from the tagged tree with git archive and uploads it when a release is published. It can also be run by hand to backfill an existing tag. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
Summary
hacs.json: setzip_release: trueandfilename: spotcast.zip, so HACS downloads a release asset instead of the auto-generated source archive.Release zipworkflow: onrelease: published, buildsspotcast.zipfrom the tagged tree (git archive HEAD:custom_components/spotcast, integration files at the zip root, as HACS extracts it straight intocustom_components/spotcast) and uploads it.workflow_dispatchwith ataginput backfills an existing release.Why
GitHub does not count downloads of source archives, so there was no way to know how many HACS installs and updates each release gets. Release assets have a per-release
download_count.Rollout
hacs.jsonat the tag it installs, so this takes effect from the first release cut after this merge. Older tags keep using the source archive.spotcast.zipwas already attached by hand to v6.6.4 (built with the samegit archivecommand, 109 entries, manifest version 6.6.4).🤖 Generated with Claude Code