Skip to content

Restore the Ruby 2.6-3.1 test checks - #902

Draft
apiology wants to merge 2 commits into
sds:mainfrom
apiology:pin-ci-runner-to-ubuntu-24.04
Draft

apiology wants to merge 2 commits into
sds:mainfrom
apiology:pin-ci-runner-to-ubuntu-24.04

Conversation

@apiology

Copy link
Copy Markdown
Contributor

Claude: This PR was written by Claude Code on behalf of @apiology.

Problem

The Ruby 2.6–3.1 test checks fail before any spec runs:

# rspec (3.0, ubuntu) › Set up Ruby 3.0
##[error]Error: Unavailable version 3.0.7 for ruby on ubuntu-26.04

Every PR now shows four red checks regardless of its change, since ubuntu-latest moved to ubuntu-26.04.

Solution

Run the workflows on ubuntu-26.04 named explicitly, with a matrix include keeping the Ruby 2.6–3.1 rows on ubuntu-24.04, where setup-ruby still provides them.

Non-ubuntu matrix rows still use <os>-latest. The explicit job name keeps check names as rspec (<ruby>, <os>), which this repo's upstream requires for merging.

apiology and others added 2 commits October 20, 2026 03:11
ubuntu-latest now resolves to ubuntu-26.04, for which setup-ruby has
no Ruby 2.6-3.1 builds ("Unavailable version 3.0.7 for ruby on
ubuntu-26.04"), so those matrix entries fail before running specs.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wo4FerFK9aaxrGrmVE9ncZ
Name ubuntu-26.04 explicitly so runners do not move when ubuntu-latest
does. setup-ruby has no Ruby 2.6-3.1 builds for ubuntu-26.04, so a
matrix include keeps those rows on ubuntu-24.04. Non-ubuntu rows still
use <os>-latest. The explicit job name keeps check names as
"rspec (<ruby>, <os>)", which upstream requires.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wo4FerFK9aaxrGrmVE9ncZ

This branch has not been deployed

No deployments
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