Stale rubocop-rspec and rspec-rails entries crash rake rubocop on Ruby 3.3

Open Beginner friendly
#68 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
86/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
ruby
Domain
build-system, ci-cd, testing-qa

Research direction

Start with the dependency entries in Gemfile and the rubocop task in Rakefile, then inspect the rake.yml workflow context. Run bundle update && bundle exec rake to confirm the Minitest suite and remaining RuboCop cops complete cleanly; done means the rake job is green without the stale RSpec extensions.

Written by the indexing model from the issue text.

Description

The Rakefile requires rubocop-rspec for the rubocop task (Rakefile:45) and the Gemfile pulls in both rspec-rails ~>6.0 (Gemfile:13) and rubocop-rspec ~>2.22 (Gemfile:18). Neither belongs here: test/zold/test_wts.rb is plain Minitest, no spec/ directory exists, and .rubocop.yml does not enable any RSpec cop. The two gems and the require are dead weight kept from a copy-pasted skeleton.

On the Ruby 3.3 CI runner the version pin resolves rubocop-rspec 2.31.0, which transitively loads rubocop-rspec_rails 2.29.1. That extension calls RuboCop::ConfigLoader.inject_defaults! against the resolved rubocop 1.87.0, and the new signature rejects the directory argument: the rake step prints warning: Use config YAML file path instead of project root directory. and raises out of rubocop-rspec_rails.rb:18. The whole test (ubuntu-24.04, 3.3) job dies after a clean Minitest run of 10 assertions, so the rake.yml workflow stays red on master at 7c79029 and on every open pull request including #62 and #64. CI failure unrelated to actual code makes badge-driven review useless and lets a real regression slip past the reviewer.

Delete gem 'rspec-rails', '~>6.0', require: false and gem 'rubocop-rspec', '~>2.22', require: false from Gemfile, and drop the task.requires << 'rubocop-rspec' line from Rakefile. Run bundle update && bundle exec rake to confirm minitest plus the remaining rubocop-rake, rubocop-minitest, rubocop-performance cops complete cleanly, then re-trigger the workflow so the rake job lands green.

Dominant language
Ruby
Stars
10
Forks
7
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from zold-io/zold-ruby-sdk

All issues in zold-io/zold-ruby-sdk

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.