Skip to content

ci(release): bump runner to ubuntu-22.04 (ubuntu-20.04 retired)#163

Merged
adequatelimited merged 1 commit intomasterfrom
release/fix-runner-20-to-22
Apr 18, 2026
Merged

ci(release): bump runner to ubuntu-22.04 (ubuntu-20.04 retired)#163
adequatelimited merged 1 commit intomasterfrom
release/fix-runner-20-to-22

Conversation

@adequatelimited
Copy link
Copy Markdown
Collaborator

Problem

The `release` workflow queues on `runs-on: ubuntu-20.04`, which was retired from GitHub-hosted runners in April 2025. As a result, the `v3.1.0-beta` release build (run 24613049633) has been sitting in `queued` state since it was created and will never pick up a runner.

Fix

  • `runs-on: ubuntu-20.04` → `ubuntu-22.04`
  • NVIDIA apt repo path `ubuntu2004` → `ubuntu2204` to match

Test plan

  • After merge, manually trigger the workflow against `v3.1.0-beta` via `gh workflow run release.yaml --ref v3.1.0-beta` (or the `workflow_dispatch` button) and verify the CUDA install + `make miner` build + artifact upload succeed.
  • Confirm the `mcmminer-v3.1.0-beta.ubuntu.cuda-12.8-570.86.10.tar.gz` asset lands on the release page.

Follow-up

If we want future releases to be tied to a specific LTS more deliberately, we can pin `ubuntu-22.04` explicitly (as done here) or move to `ubuntu-24.04` — either works for CUDA 12.8; 22.04 is the closer compatibility hop from 20.04.

GitHub deprecated ubuntu-20.04 hosted runners in April 2025; queued
jobs targeting that label never get assigned, so the v3.1.0-beta
release run has been stuck in 'queued' indefinitely.

Also updates the NVIDIA cuda-keyring URL from the ubuntu2004 repo path
to ubuntu2204 to match the new runner.
@adequatelimited adequatelimited merged commit bbbacea into master Apr 18, 2026
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant