Attach virtual-appliance images to the release - #9
Merged
Conversation
Link the appliance build to the release: appliance.yml now runs on
'release: published' (and never blocks the release - it attaches to the already-
published one). It gzips the Hyper-V VHDX (2 GB asset cap) and uploads
dispatch-appliance-<ver>-{hyperv.vhdx.gz,vmware.ova,kvm.qcow2} to the release,
skipping any file over 2 GB with a warning. A manual run can target an existing
release via the release_tag input; without it, behavior is unchanged (CI artifacts).
Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Fixes the gap that the release has no Hyper-V (or other appliance) download and the download page doesn't link one. The appliance images were only being produced as short-lived CI artifacts by
appliance.yml.Approach (per the request: link to the release, but run after it)
appliance.ymlnow also triggers onrelease: published— so it runs after the release is out and attaches the images to it, never blocking or racing the (fast) release jobs. It can also be dispatched manually with arelease_taginput to populate an existing release.When linked to a release it uploads:
dispatch-appliance-<ver>-hyperv.vhdx.gz(Hyper-V)dispatch-appliance-<ver>-vmware.ova(VMware)dispatch-appliance-<ver>-kvm.qcow2(KVM/Proxmox)The Hyper-V VHDX is gzipped because GitHub caps release assets at 2 GB/file; any file still over 2 GB is skipped with a
::warning::rather than failing the job. Without a release context, behavior is unchanged (CI artifacts only).After merge
Run
gh workflow run appliance.yml -f release_tag=v0.5.0to build + attach the appliances to the existing v0.5.0 release (this also reveals the real image sizes). Then the download page gets the actual asset links (follow-up).🤖 Generated with Claude Code