fix(ci): use github-script for wheel pruning instead of gh CLI#354
Merged
fix(ci): use github-script for wheel pruning instead of gh CLI#354
Conversation
The gh CLI is not available on the bare build-amd64 runner (only in the CI container image), causing 'gh release view' to fail silently and skip pruning every time. Switch to actions/github-script which uses the built-in Octokit client and needs no external CLI tools. Tested via a temporary debug workflow on this branch that confirmed the github-script approach successfully lists all 25 devel release assets (21 stale wheels across 7 versions).
drew
force-pushed
the
fix/debug-wheel-pruning
branch
from
5240a2c to
5aa0035
Compare
drew
approved these changes
Mar 16, 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
2 participants
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
ghCLI calls withactions/github-script@v7for pruning stale wheel assets from the devel releaseghCLI is not installed on the barebuild-amd64runner (only inside the CI container image), sogh release viewwas silently failing every run (fix(ci): prune stale devel wheel assets #332, fix(ci): run wheel pruning before moving devel tag #334)github-scriptaction uses the built-in Octokit client and needs no external CLI toolsRoot Cause
The
release-develjob runs onbuild-amd64without a container, unlike most other jobs which useghcr.io/nvidia/openshell/ci:latest. TheghCLI is only available inside that container. The pruning step's guard clause (gh release view ... > /dev/null 2>&1) swallowed the error and always hit the "No existing devel release found" bail-out.Verification
Tested with a temporary
github-scriptdebug workflow on this branch (run #23135749664) that confirmed:Changes
.github/workflows/release-dev.yml: Replaced thePrune stale wheel assets from devel releasestep from a bash script usingghCLI to anactions/github-script@v7step using OctokitTesting
github-scriptcan list devel release assets from the same runner environment