Ruby-LSP and Ruby-LSP-Rails downgrade randomly

[stathis-alexander]

Description

Ruby LSP Information

This is a strange bug that I'm not sure how to reproduce, but I've been experiencing it for a while. Sometimes, the Ruby-LSP gem versions will randomly resolve and downgrade to v0.11.2. It seems to happen most often when I restart Ruby-LSP after updating the Gemfile or other gems. I am logging it here in case others are experiencing it also, or if others have figured out what causes and resolves it.

If I then cd into the .ruby-lsp directory and run bundle update, I can reverse the behavior.

I think it is related to the versions of other dependencies, but there's something weird about how they're setup so that they resolve incorrectly.

❯ cd .ruby-lsp
❯ bundle update ruby-lsp
Fetching gem metadata from https://gems.graphql.pro/..
Fetching gem metadata from https://gems.contribsys.com/..
Fetching gem metadata from https://gem.fury.io/angellist/...
Fetching gem metadata from https://rubygems.pkg.github.com/angellist/..
Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Resolving dependencies...
Using logger 1.6.2 (was 1.6.1)
Using ruby-lsp 0.11.2 (was 0.22.1)
Using ruby-lsp-rails 0.2.6 (was 0.3.27)
Note: ruby-lsp version regressed from 0.22.1 to 0.11.2
Bundle updated!
2 installed gems you directly depend on are looking for funding.
  Run `bundle fund` for details
❯ bundle update ruby-lsp
Fetching gem metadata from https://gems.graphql.pro/..
Fetching gem metadata from https://gems.contribsys.com/..
Fetching gem metadata from https://gem.fury.io/angellist/...
Fetching gem metadata from https://rubygems.pkg.github.com/angellist/..
Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Resolving dependencies...
Using ruby-lsp 0.22.1 (was 0.11.2)
Using ruby-lsp-rails 0.3.27 (was 0.2.6)
Bundle updated!
2 installed gems you directly depend on are looking for funding.
  Run `bundle fund` for details

[andyw8]

👋 Thank you for the report.

Just to rule out anything obvious, can you ensure you're on the latest release of bundler?

[stathis-alexander]

We only upgrade bundler versions every so often to prevent annoying lock file changes, but I think we did recently:

❯ bundler --version
Bundler version 2.5.22