ci: install the tools release jobs need on self-hosted runners - #1774
Merged
Merged
Conversation
Publish-Module needs the dotnet CLI, which the self-hosted runners lack, so the PowerShell module failed to publish; set it up as the validate job does. Create GitHub Release uses the GitHub CLI, so fetch a pinned, checksum-verified copy when the runner has none. Co-Authored-By: Claude Opus 5.5 (1M context) <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.
Part of #1773.
Problem
Re-running the v0.15.0 release (run 35842615256, attempt 2) built, pushed and signed all three images and created the bundle. Two jobs then failed, and both are first-time self-hosted problems:
Publish-Moduleneeds thedotnetCLI ("dotnet command version '2.0.0' or newer is required"). GitHub-hosted runners have it; these self-hosted runners don't, and this job never set it up. Nothing reached PSGallery.github-pagesenvironment only allowed themainandgh-pagesbranches. The job was added after v0.14.0 (ci: deploy the docs site via the GitHub Actions Pages pipeline #1265), so v0.15.0 is the first tag to try it. Fixed in settings, not here: the environment now also allowsv*tags.Fix
publish-powershellruns the same pinnedactions/setup-dotnetstep the validate job uses.create-release(not yet reached) usesgh release create. A new step uses the runner'sghif it has one. Otherwise it downloads the GitHub CLI 2.97.0 (the devcontainer's version), verifies its SHA-256, and adds it to the job's PATH.Evidence
gh version 2.97.0.Docs: n/a - CI only.
🤖 Generated with Claude Code