Repository navigation
fix ci: use latest ruby 3.2.x in setup-ruby - #161
Merged
Merged
Conversation
ubuntu-latest moved to 26.04, where ruby-builder only publishes the newest patch release of each series. .ruby-version pins 3.2.2, which no longer has a prebuilt binary, so Setup Ruby fails with a 404. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This branch was successfully deployed
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.
El deploy está fallando en todas las PRs (no es un problema de ninguna rama en particular):
ubuntu-latestpasó a ser ubuntu-26.04, yruby-buildersolo publica el último patch de cada serie para esas imágenes. Como.ruby-versionpinnea3.2.2,ruby/setup-rubytira 404.Le paso
ruby-version: '3.2'explícito al step, así siempre agarra el último 3.2.x disponible. No toco.ruby-versionpara no romperle el entorno local a nadie.Nota: el workflow corre también con
pull_request_target, que usa la definición del workflow de la rama base. Así que las PRs abiertas van a seguir mostrando ese check en rojo hasta que esto esté mergeado enmain.🤖 Generated with Claude Code