Repository navigation
Fix deploy: use latest Ruby 3.2.x - #28
Merged
Merged
Conversation
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.
Deploy sitefails at Setup Ruby sinceubuntu-latestmoved to Ubuntu 26.04:ruby/setup-rubyhas no 3.2.2 build for that image (Unavailable version 3.2.2 for ruby on ubuntu-26.04; only the latest patch, 3.2.11, is built). The last successful deploy was 2026-10-26; the deploy of #27 (run 40938292677) failed at this step.This sets
ruby-version: "3.2", which selects the latest 3.2.x, as the setup-ruby error message recommends. The repo has noGemfile.lock, so nothing else pins the Ruby patch version.