Conversation
The release step was failing because gh CLI is not available inside the ci-base container. Split the workflow into two jobs: - test-and-publish: Runs in container, prepares release metadata artifact - create-releases: Runs on runner (no container), uses gh to create releases
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.
Problem
CI was failing with
gh: not foundbecause the GitHub CLI is not available inside theci-basecontainer where all steps execute.Solution
Split the release step into a separate job that runs directly on the runner (no container) where
ghis available:ghto create releasesThis maintains the same functionality while ensuring
ghis available when needed.