Repository navigation
ci: attach the HRX portable packages to releases as a preview - #773
Merged
Merged
Conversation
The HRX portable builds have been produced on every run but never reached a release. Each platform now gets a release-hrx job that publishes them under an HRX_ prefix next to the default assets: HRX_fastflowlm_<version>_linux.tar.gz HRX_fastflowlm_<version>_windows_amd64.zip They are separate jobs rather than extra needs on the existing release jobs, so a failed HRX build leaves the release without the HRX asset instead of holding back the default ones. The Linux release job downloaded every artifact in the run and uploaded portable/**/*.gz, which since the models-from-source build was added would also have attached models-from-source_fastflowlm_<version>_linux.tar.gz, and the HRX tarball whenever its job finished first. It now downloads the "portable" artifact by name and uploads only fastflowlm_*_linux.tar.gz. The model sweep's release mode now looks for the HRX assets too and sweeps them when present, instead of always skipping HRX on a dispatch. Co-Authored-By: Claude <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
The HRX portable builds are produced on every CI run but have never been attached to a release. This PR publishes them as a preview, next to the default assets:
HRX_fastflowlm_<version>_linux.tar.gzHRX_fastflowlm_<version>_windows_amd64.zipThe packages use the same layout as the default portable packages, so they install the same way.
Changes
debian-portable.yml/windows-build.yml: add arelease-hrxjob on each platform. Each job runs only on tags and needs only its HRX build. It is a separate job, not an extraneeds:entry on the existingreleasejob, so if the preview HRX build fails, the release just goes out without the HRX asset and the default assets are not held back.debian-portable.yml, bug fix: the Linuxreleasejob downloaded every artifact in the run and uploadedportable/**/*.gz. The models-from-source build added in Add the Gemma 4 model code #763 runs in that same job, so the next tag would have attachedmodels-from-source_fastflowlm_<version>_linux.tar.gzto the release. The HRX tarball would also have been attached whenever its job happened to finish first. The job now downloads theportableartifact by name and uploads onlyfastflowlm_*_linux.tar.gz.model-sweep.yml: in release mode (workflow_dispatch), the sweep now checks for theHRX_*assets and sweeps them when they are present. Before, it always skipped HRX in release mode. In run mode, the HRX sweeps work as before.Test plan
.debs, and the twoHRX_*assets. Themodels-from-source_*tarball must not be attached.sweep-linux-hrxandsweep-windows-hrxrun.🤖 Generated with Claude Code