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
{{ message }}
Repository navigation
Updating Package does not update new Ruby Versions list #447
I use this plugin to manage my ruby versions, and a repo I constantly work in just updated to ruby 3.4.3. I ran asdf plugin update ruby per the docs, but then when I ran asdf list all ruby | grep 3.4 I got this:
No 3.4.3 in the list. After about 30 mins of troubleshooting, I decided to uninstall and re-install the plugin and now I see 3.4.3 in the list.
So it appears that the asdf plugin update ruby does not actually update the ruby versions that are available for download.
I'm hitting the same issue and for some reason the ASDF_RUBY_BUILD_VERSION in ~/.asdf/plugins/ruby/lib/utils.sh is downgraded? I didn't do this manually:
~/.asdf/plugins/ruby/ruby-build (git)-[master] % git status
On branch master
Your branch is up to date with 'origin/master'.
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
modified: ../lib/utils.sh
~/.asdf/plugins/ruby (git)-[master] % git restore --staged lib/utils.sh fixed it.
Reacted by Sergey Kovalev, rud, Filipe Mendes da Rocha Lopes, kreintjes, fell sunderland, Daniel, Robert Shecter, Ferran Pelayo Monfort, Pedro Silva, Shaun Whitely and 1 more
Reacted by fell sunderland, Daniel, Robert Shecter, Ferran Pelayo Monfort, Nate Eizenga and terasawa
I'm hitting the same issue and for some reason the ASDF_RUBY_BUILD_VERSION in ~/.asdf/plugins/ruby/lib/utils.sh is downgraded? I didn't do this manually:
~/.asdf/plugins/ruby/ruby-build (git)-[master] % git status
On branch master
Your branch is up to date with 'origin/master'.
Changes to be committed:
(use "git restore --staged ..." to unstage)
modified: ../lib/utils.sh
~/.asdf/plugins/ruby/ruby-build (git)-[master] % git diff --cached
diff --git a/lib/utils.sh b/lib/utils.sh
index 31d322e..aa9be9b 100644
--- a/lib/utils.sh
+++ b/lib/utils.sh
@@ -1,6 +1,6 @@
#!/usr/bin/env bash
I'm seeing the same dirty state in the plugin folder after running asdf plugin update ruby. What version of asdf are you all using? I saw this behavior with 0.16.7.
I suspect it's an asdf issue, rather than a Ruby plugin issue, but I don't know enough about the inner workings to know for sure.
Reacted by rud, fell sunderland and Robert Shecter
I'm hitting the same issue and for some reason the ASDF_RUBY_BUILD_VERSION in ~/.asdf/plugins/ruby/lib/utils.sh is downgraded? I didn't do this manually:
~/.asdf/plugins/ruby/ruby-build (git)-[master] % git status
On branch master
Your branch is up to date with 'origin/master'.
Changes to be committed:
(use "git restore --staged ..." to unstage)
modified: ../lib/utils.sh
~/.asdf/plugins/ruby (git)-[master] % git restore --staged lib/utils.sh fixed it.
This worked for me. Is it possible one or more the following .gitconfig options could be related to the issue, e.g. by unexpectedly stashing/popping a change onto the updated ruby-build branch? Do others experiencing this have these in their config as well?
Activity
rnestler commentedon Apr 23, 2025
I'm hitting the same issue and for some reason the
ASDF_RUBY_BUILD_VERSIONin~/.asdf/plugins/ruby/lib/utils.shis downgraded? I didn't do this manually:~/.asdf/plugins/ruby (git)-[master] % git restore --staged lib/utils.shfixed it.serg-kovalev commentedon Apr 23, 2025
Exactly, the solution was to hard reset back and pull the latest changes. Now it works fine
juanpaco commentedon Apr 24, 2025
I'm seeing the same dirty state in the plugin folder after running
asdf plugin update ruby. What version ofasdfare you all using? I saw this behavior with0.16.7.I suspect it's an
asdfissue, rather than a Ruby plugin issue, but I don't know enough about the inner workings to know for sure.dup2 commentedon Apr 25, 2025
Same problem here - seems like this is a real issue for everybody. Also using
0.6.17of asdf via homebrew.kreintjes commentedon Apr 30, 2025
Same problem over here. I'm also using asdf 0.16.7.
rnestler's suggestion fixed it :)
MatheusRich commentedon May 9, 2025
This fixed it for me:
$ rm -r ~/.asdf/installs/ruby/3.4.3 $ ASDF_RUBY_BUILD_VERSION=master asdf install ruby 3.4.3eizengan commentedon May 28, 2025
This worked for me. Is it possible one or more the following
.gitconfigoptions could be related to the issue, e.g. by unexpectedly stashing/popping a change onto the updated ruby-build branch? Do others experiencing this have these in their config as well?exterm commentedon Jul 28, 2025
It seems that
asdfshould at least output some kind of error when there are staged changes in a plugin and you're running update