I recently added ruby-lsp-rspec and ruby-lsp-factory_bot gems to my Gemfile, which added ruby-lsp to my Gemfile.lock as a transitive dependency. Unfortunately, that seems to stop ruby-lsp from auto-updating in its composed bundle, .ruby-lsp/Gemfile.lock still has the locked version from the project's Gemfile.lock.
This is probably not a bug, because I imagine it's harder for Ruby LSP to know whether you want the ruby-lsp version locked. I just found it really convenient that Ruby LSP doesn't need to be added to the Gemfile and that it auto-updates, so I don't want to lose that just because I installed addons.
My proposal is that Ruby LSP always tries to auto-update to latest version allowed by the project's Gemfile (in .ruby-lsp/Gemfile.lock). That way if users still want to lock ruby-lsp to a certain version and prevent auto-updates, they can lock it in the Gemfile. This seems like a reasonable requirement to me.
I recently added
ruby-lsp-rspecandruby-lsp-factory_botgems to my Gemfile, which addedruby-lspto myGemfile.lockas a transitive dependency. Unfortunately, that seems to stopruby-lspfrom auto-updating in its composed bundle,.ruby-lsp/Gemfile.lockstill has the locked version from the project'sGemfile.lock.This is probably not a bug, because I imagine it's harder for Ruby LSP to know whether you want the
ruby-lspversion locked. I just found it really convenient that Ruby LSP doesn't need to be added to the Gemfile and that it auto-updates, so I don't want to lose that just because I installed addons.My proposal is that Ruby LSP always tries to auto-update to latest version allowed by the project's
Gemfile(in.ruby-lsp/Gemfile.lock). That way if users still want to lockruby-lspto a certain version and prevent auto-updates, they can lock it in theGemfile. This seems like a reasonable requirement to me.