Repository navigation
ci: use gh CLI to attach .deb to release - #5
Merged
Merged
Conversation
Replace softprops/action-gh-release@v2, which is disallowed by the enterprise Actions policy, with the preinstalled gh CLI. Creates the release if missing (tolerating the race between matrix jobs) and uploads each package with --clobber for idempotent re-runs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
ghjklw
approved these changes
Sep 1, 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.
Problem
The
Build .deb packageworkflow fails at the release step:Fix
Replace the disallowed third-party action with the
ghCLI, which is preinstalled on GitHub-hosted runners and requires no allow-listing.ubuntu-22.04/ubuntu-24.04).gh release upload --clobberso both matrix packages attach to the same tag and re-runs are idempotent.github.token; the existingcontents: writepermission is sufficient.No other workflow references the disallowed action.