-
Notifications
You must be signed in to change notification settings - Fork 69
Ruby version ignored #32
Comments
Hey @fbjork are you still having this problem or has it been resolved? |
I got past that error, but now I'm getting this error:
|
The only Rubies available from the 'toolcache' are 2.4.6, 2.5.5, and 2.6.3. The current 'setup-ruby' actions relies using Rubies on the disk image. This may change or be extended in the future. Since Ruby binaries are relatively small, you can use https://github.com/eregon/use-ruby-action, which downloads and installs all Ruby standard releases from 2.3.0 forward. |
They upgraded some Ruby versions. Maybe use the format '2.6.x'? See https://github.com/MSP-Greg/github-actions-ruby-info/runs/393668457 At present, the versions are not aligned across OS's... |
Am I missing something fundamental here? How can my workflow work with this action one day, and not the next, when I'm pinned to a major version of the action? If they removed some versions why wasn't the major version bumped? Does this not work like I think it works? How do I make a workflow that will work tomorrow as well as today? |
What was your |
It was specifically |
teeny. Anyway, nothing is wrong with that. I'm just the messenger... |
Ruby 2.7.0 is now installed |
The readme has been updated to clarify the virtual environments in the action hosted machines pools only maintain latest of each minor version. This setup-action operates on the versions installed on the VM images. There is a proposal in ADR #49 discussing options to pull versions JIT but right now there's no official distributions of ruby. Options are being discussing in the VM issue and ADR. For now, bind to minor. Hope that helps. Apologies for your issues. Closing but let me know if any of that is not clear. |
I have the following in my config, but the Ruby version defaults to 2.6.3
Any idea what's wrong?
This is the output:
The text was updated successfully, but these errors were encountered: