fix(ci): pass wheel filenames as job output instead of re-downloading#418
Merged
fix(ci): pass wheel filenames as job output instead of re-downloading#418
Conversation
88c343d to
2c64396
Compare
The trigger-wheel-publish job was downloading the wheel artifact onto a persistent self-hosted runner just to glob the filenames. Since download-artifact does not clean the destination directory, stale .whl files from every previous run accumulated in release/ and were all sent to GitLab as WHEEL_FILENAMES. Confirmed on the runner: /home/ubuntu/actions-runner/_work/OpenShell/ OpenShell/release/ contained 120+ wheels spanning versions 0.0.5 through 0.0.10. Fix: capture wheel filenames as a job output in build-python-wheels and pass them directly to trigger-wheel-publish. The trigger job no longer downloads the artifact at all — it only needs the filenames to construct GitHub release asset URLs for GitLab/Kitmaker.
2c64396 to
bcd0a20
Compare
drew
approved these changes
Mar 18, 2026
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
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
Passes wheel filenames as a job output from
build-python-wheelstotrigger-wheel-publishinstead of re-downloading the artifact.Root Cause
The
trigger-wheel-publishjob runs on a persistent self-hosted runner (agent-dev-kit-build-1) with noactions/checkoutstep. It was downloading the wheel artifact intorelease/just to glob the filenames. Sincedownload-artifactdoes not clean the destination directory, stale.whlfiles from every previous run accumulated there.Confirmed on the runner instance:
contained 120+ wheels spanning versions 0.0.5 through 0.0.10, while the actual artifact only contained 3 wheels (~5MB each).
Fix
build-python-wheelsthat writes the comma-separated basenames to$GITHUB_OUTPUTtrigger-wheel-publishreadsneeds.build-python-wheels.outputs.wheel_filenamesdirectly — no download, no filesystem, no accumulation possible