Update outdated versions used in CI - #3034
Merged
Merged
Conversation
soutaro
force-pushed
the
claude/ci-ruby-version-check-4v4bw0
branch
2 times, most recently
from
July 27, 2026 04:34
4534250 to
ac84a35
Compare
Ruby 3.2 reached EOL on 2026-04-01, and several tool versions pinned in the workflows had fallen behind. * Drop Ruby 3.2 from the test matrix. The README already states that the library code targets non-EOL versions of Ruby (`>= 3.3` as of 2026), and `docs/CONTRIBUTING.md` noted the 3.2 entry as something the CI retained. `required_ruby_version` is left alone here. * Run the type check and the Windows compile job on Ruby 4.0, the version the rest of the workflows already use. * Point the LLVM apt repository at noble instead of jammy: `ubuntu-latest` is Ubuntu 24.04, so the jammy packages no longer matched the runner. Install the signing key into a keyring instead of the deprecated `apt-key`. * Bump re2c 4.3 -> 4.5.1. The generated `src/lexer.c` is unchanged apart from the version banner. * Bump wasmtime v45.0.2 -> v47.0.2 for the WebAssembly smoke test. * Bump the JRuby image in Dockerfile.jruby 10.0.6 -> 10.1.1.0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TFnHiHNVLno7GWwjXJqDx4
soutaro
force-pushed
the
claude/ci-ruby-version-check-4v4bw0
branch
from
July 27, 2026 04:43
ac84a35 to
10e3c8b
Compare
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
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.
Ruby 3.2 reached EOL on 2026-04-01, and several tool versions pinned in the workflows had fallen behind.
The RDoc side of this (the
comments.ymlRuby pin and the regeneratedcore/stdlibcomments) was split out into #3035, which is already merged. This PR is rebased on top of it and no longer touchescomments.yml.Ruby versions
ruby.ymltest matrix. Ruby 3.2 went EOL on 2026-04-01, and the README already states that the library code targets non-EOL versions of Ruby (>= 3.3as of 2026). The note indocs/CONTRIBUTING.mdthat said the CI retains Ruby 3.2 tests is updated to match.typecheck.yml) and the Windows compile job (windows.yml) on Ruby 4.0, which the rest of the workflows already use.required_ruby_versionin the gemspec stays at>= 3.2— this PR only changes what the CI runs.Tool versions
ubuntu-latestis Ubuntu 24.04, soc-check.ymlwas pulling clang-format packages built for 22.04. Both repositories ship clang-format20.1.8, so the formatting itself is unaffected. While here, the signing key goes into a keyring instead of the deprecatedapt-key, and the source is written to/etc/apt/sources.list.d/directly —add-apt-repositoryon 24.04 rejects[signed-by=...]inside a one-linedebshortcut.src/lexer.re: afterclang-format, the generatedsrc/lexer.cis byte-identical apart from the/* Generated by re2c ... */banner, so only that line changes here andconfirm_lexerstays green.wasmtime run --invoke, whichrake wasm:checkrelies on, is still supported.Dockerfile.jruby.WASI SDK 33 is still the current release, so it is left alone.
Deliberately not included
steep/Gemfilestill pinssteep ~> 1.10andrbs ~> 3.9(locked at steep 1.10.0 / rbs 3.10.4) while steep 2.0.0 and rbs 4.0.3 are out. A major steep bump is likely to surface new diagnostics, so it deserves a separate PR.actions/cachev5 → v6 — already covered by Bump actions/cache from 5 to 6 #3021, and Pin GitHub Actions to commit hashes #3020 is reworking how actions are pinned, so no action versions are touched here.RUBY_VERSION >= '3.2'guards left inlib/andtest/are now always true; cleaning them up is a separate change.🤖 Generated with Claude Code