Ruby Version Detection

[apainintheneck]

I've found some unexpected behavior with automatic Ruby version detection when using standard with my project.

The docs say that the Ruby version is inferred from any .ruby-version, .tool-versions, Gemfile.lock, and *.gemspec files that might be present (reference) which makes me think that I don't need to specify it explicitly since there is a gemspec for project.

The most recent upgrade from standard 1.47.0 to 1.49.0 caused the linter to fail on Ruby 3.4 with these errors while succeeding on previous Ruby versions.

lib/rfc_reader/command.rb:99:38: Style/ItBlockParameter: Use `it` block parameter.
lib/rfc_reader/command.rb:101:34: Style/ItBlockParameter: Use `it` block parameter.
lib/rfc_reader/error_context.rb:53:18: Style/ItBlockParameter: Use `it` block parameter.
lib/rfc_reader/search.rb:88:22: Style/ItBlockParameter: Use `it` block parameter.
lib/rfc_reader/search.rb:89:23: Style/ItBlockParameter: Use `it` block parameter.

• Related PR: Bump standard from 1.47.0 to 1.49.0 apainintheneck/rfc-reader#45

I'm assuming that the problem here is that it's detecting Ruby 3.4 for some reason and basing the rules on that Ruby version instead of using the minimum Ruby version defined in the gemspec.

It's not obvious to me if this is intended behavior, a bug in rubocop or a bug in standard but I figured that I'd open an issue here first to see if you had any ideas.

Also, I did try setting the Ruby version explicitly by creating a .standard.yml file with ruby_version: 3.0 and then it worked as expected.

[jasonkarns]

Would you be able to add rubocop -V to the environment where standard is being run? Recent versions of rubocop will print additional ruby-version information in that output.

rubocop/rubocop#13311

Additionally, if you're amenable to it, this little rake task can print not only which ruby version is being targeted, but also which file is directing it.

https://gist.github.com/jasonkarns/f25751dde72963e7b13c7bf75de44bee

You're right this looks like a bug, but I'm not sure yet whose bug it is :D

[apainintheneck]

Passing in the -V option returns the following info.

~/D/c/p/rfc-reader (dependabot/bundler/standard-1.49.0|✔) $ ruby -v
ruby 3.4.2 (2025-02-15 revision d2930f8e7a) +PRISM [x86_64-linux]
~/D/c/p/rfc-reader (dependabot/bundler/standard-1.49.0|✔) $ bundle exec standardrb -V
Standard version: 1.49.0
RuboCop version:  1.75.2 (using Parser 3.3.7.4, rubocop-ast 1.44.1, analyzing as Ruby 3.0, running on ruby 3.4.2) [x86_64-linux]
~/D/c/p/rfc-reader (dependabot/bundler/standard-1.49.0|✔) $ bundle exec standardrb
standard: Use Ruby Standard Style (https://github.com/standardrb/standard)
  lib/rfc_reader/command.rb:99:38: Style/ItBlockParameter: Use `it` block parameter.
  lib/rfc_reader/command.rb:101:34: Style/ItBlockParameter: Use `it` block parameter.
  lib/rfc_reader/error_context.rb:53:18: Style/ItBlockParameter: Use `it` block parameter.
  lib/rfc_reader/search.rb:88:22: Style/ItBlockParameter: Use `it` block parameter.
  lib/rfc_reader/search.rb:89:23: Style/ItBlockParameter: Use `it` block parameter.
standard: Run `standardrb --fix` to fix up to 5 problems.

Running the Rake task returns Ruby v3.0.

~/D/c/p/rfc-reader (dependabot/bundler/standard-1.49.0|✚1) $ rake rubocop:ruby
3.0

Let me know if there's anything else I can run to make things clearer.

[jasonkarns]

The -V option is for rubocop. Since that's what does the underlying work, I'm looking to see what version it sees.

[apainintheneck]

Like this?

$ bundle exec rubocop -V
1.75.2 (using Parser 3.3.7.4, rubocop-ast 1.44.1, analyzing as Ruby 3.0, running on ruby 3.4.2) [x86_64-linux]

[jasonkarns]

Yep thank you.

analyzing as Ruby 3.0

That's the bit that indicates rubocop is detecting the correct Ruby version. Which indicates the bug is very likely in standard itself.