You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The plugin hasn't updated its ruby-build version yet.
By default asdf-ruby uses a recent release of ruby-build, however instead you can choose your own branch/tag through the ASDF_RUBY_BUILD_VERSION variable:
This is how I was able to resolve the issue on my end:
% asdf plugin remove ruby
% asdf plugin add ruby
% asdf list all ruby | grep 3.4.4
3.4.4
I believe the same issue occurred before as well. #442
Reacted by Beverly Guillermo, Randy Burgess, Lloyd Pick, Olivier, Antoine Ménard, Julian Kornberger, Sam, Matthew Bender, Konstantin Mochalov, Todd and 25 more
Reacted by Hugo Melo, Jacob Feldman, Jorge Marizan, armg-yuma-ito, Hein du Toit, Paul, Henrique, em, Wihan Nel · he/him and Eduardo Moura
Reacted by Wihan Nel · he/him, Eduardo Moura and João Monteiro
Adding some documentation to ruby-build for how to install a version of ruby that might not yet be bundled in ruby-build: rbenv/ruby-build#2537
Might be worthwhile to document the following in asdf-ruby as well. (Even better, if asdf-ruby bundled its own directory that was prepended to RUBY_BUILD_DEFINITIONS, and allowed users to drop custom defs in there without mutating any variables. Wouldn't need to be exported if the var were set by asdf-ruby plugin prior to invoking ruby-build commands.)
# could be any directory, but would be best if bundled by asdf-rubyexport RUBY_BUILD_DEFINITIONS=/opt/asdf/share/ruby-build
# "custom" build definition in that shared location:
$ cat $RUBY_BUILD_DEFINITIONS/3.4.4
install_package "openssl-3.0.16""https://github.com/openssl/openssl/releases/download/openssl-3.0.16/openssl-3.0.16.tar.gz#57e03c50feab5d31b152af2b764f10379aecd8ee92f16c985983ce4a99f7ef86" openssl --if needs_openssl:1.0.2-3.x.x
install_package "ruby-3.4.4""https://cache.ruby-lang.org/pub/ruby/3.4/ruby-3.4.4.tar.gz#a0597bfdf312e010efd1effaa8d7f1d7833146fdc17950caa8158ffa3dcbfa85" enable_shared standard
$ asdf install ruby 3.4.4
Same here, asdf plugin update --all did not help, however, the workaround mentioned in #442
worked flawlessly, without the need of reinstalling anything:
cd ~/.asdf/plugins/ruby/
git reset .
git restore .
git pull
asdf plugin update ruby and asdf plugin update --all didn't work for me to resolve this issue for 3.4.5. Nor did Virus-X's clean git pull steps. I had to run kakikubo's
Activity
skull-squadron commentedon May 15, 2025
rbenv/ruby-build#2535
Edit: A workaround is to fork asdf-ruby and ruby-build to add the updates yourself.
stako commentedon May 16, 2025
The plugin hasn't updated its ruby-build version yet.
By default asdf-ruby uses a recent release of ruby-build, however instead you can choose your own branch/tag through the
ASDF_RUBY_BUILD_VERSIONvariable:ASDF_RUBY_BUILD_VERSION=master asdf install ruby 3.4.4jasonkarns commentedon May 16, 2025
Don't even need to fork. Ruby-build can load definition files from multiple locations. You can make the definition file yourself without even forking.
n-rodriguez commentedon May 16, 2025
Ruby 3.4.4 has been released in ruby-build repo : rbenv/ruby-build#2535 (comment)
kakikubo commentedon May 17, 2025
This is how I was able to resolve the issue on my end:
% asdf plugin remove ruby % asdf plugin add ruby % asdf list all ruby | grep 3.4.4 3.4.4I believe the same issue occurred before as well.
#442
MatheusRich commentedon May 21, 2025
Related: #447
jasonkarns commentedon May 22, 2025
Adding some documentation to ruby-build for how to install a version of ruby that might not yet be bundled in ruby-build: rbenv/ruby-build#2537
Might be worthwhile to document the following in asdf-ruby as well. (Even better, if asdf-ruby bundled its own directory that was prepended to
RUBY_BUILD_DEFINITIONS, and allowed users to drop custom defs in there without mutating any variables. Wouldn't need to be exported if the var were set by asdf-ruby plugin prior to invoking ruby-build commands.)bjliu commentedon Jul 28, 2025
same issue with 3.4.5, had to follow @kakikubo's instructions.
n-rodriguez commentedon Jul 28, 2025
did you try this :
asdf plugin update --all?Virus-X commentedon Sep 5, 2025
Same here,
asdf plugin update --alldid not help, however, the workaround mentioned in #442worked flawlessly, without the need of reinstalling anything:
michaeldhopkins commentedon Sep 10, 2025
asdf plugin update rubyandasdf plugin update --alldidn't work for me to resolve this issue for 3.4.5. Nor did Virus-X's clean git pull steps. I had to run kakikubo'saep-sunlife commentedon Oct 8, 2025
Still missing v3.4.7.
MatheusRich commentedon Oct 9, 2025
I just moved to mise instead. Not the solution to this problem, the migration is pretty easy.
wrburgess commentedon Oct 10, 2025
I moved, as well. I liked asdf over the years, but I can't fool around with waiting on ruby upgrades like this anymore.
louis-antonopoulos commentedon Oct 16, 2025
The solution referenced above worked for 3.4.7:
ASDF_RUBY_BUILD_VERSION=master asdf install ruby 3.4.7