Skip to content

CI against Ruby 3.4#351

Merged
koic merged 1 commit intorubocop:masterfrom
koic:ci_against_ruby_34
Dec 28, 2024
Merged

CI against Ruby 3.4#351
koic merged 1 commit intorubocop:masterfrom
koic:ci_against_ruby_34

Conversation

@koic
Copy link
Copy Markdown
Member

@koic koic commented Dec 28, 2024

Ruby 3.4 has been released, and support for Ruby 3.4.0 and 3.4.1 was added to setup-ruby: ruby/setup-ruby#679

rubocop/rubocop#13297 is required to pass the following spec on both Ruby versions before 3.3 and 3.4 and later:

  1) RuboCop::ConfigStore.for always uses config specified in command line
     Failure/Error: expect(config_store.for('file1')).to eq('merged {:options_config=>true}')

       expected: "merged {:options_config=>true}"
            got: "merged {options_config: true}"

       (compared using ==)
     # ./spec/rubocop/config_store_spec.rb:25:in 'block (3 levels) in <top (required)>'
     # tasks/spec_runner.rake:83:in 'RuboCop::SpecRunner::ParallelRunner#run_worker'
     # tasks/spec_runner.rake:38:in 'block in RuboCop::SpecRunner#run_specs'
     # tasks/spec_runner.rake:52:in 'RuboCop::SpecRunner#with_encoding'
     # tasks/spec_runner.rake:36:in 'RuboCop::SpecRunner#run_specs'
     # tasks/spec_runner.rake:164:in 'block in <top (required)>'

https://github.com/rubocop/rubocop-ast/actions/runs/12529029565/job/34944210256

Therefore, RuboCop used in rubocop_specs has been updated to v1.69.2, the version released with Ruby 3.4.

@koic koic force-pushed the ci_against_ruby_34 branch 3 times, most recently from cf01ff9 to 02a685a Compare December 28, 2024 19:28
Ruby 3.4 has been released, and support for Ruby 3.4.0 and 3.4.1 was added to setup-ruby:
ruby/setup-ruby#679

rubocop/rubocop#13297 is required to pass the following spec
on both Ruby versions before 3.3 and 3.4 and later:

```console
  1) RuboCop::ConfigStore.for always uses config specified in command line
     Failure/Error: expect(config_store.for('file1')).to eq('merged {:options_config=>true}')

       expected: "merged {:options_config=>true}"
            got: "merged {options_config: true}"

       (compared using ==)
     # ./spec/rubocop/config_store_spec.rb:25:in 'block (3 levels) in <top (required)>'
     # tasks/spec_runner.rake:83:in 'RuboCop::SpecRunner::ParallelRunner#run_worker'
     # tasks/spec_runner.rake:38:in 'block in RuboCop::SpecRunner#run_specs'
     # tasks/spec_runner.rake:52:in 'RuboCop::SpecRunner#with_encoding'
     # tasks/spec_runner.rake:36:in 'RuboCop::SpecRunner#run_specs'
     # tasks/spec_runner.rake:164:in 'block in <top (required)>'
```

https://github.com/rubocop/rubocop-ast/actions/runs/12529029565/job/34944210256

Therefore, RuboCop used in `rubocop_specs` has been updated to v1.69.2,
the version released with Ruby 3.4.
@koic koic force-pushed the ci_against_ruby_34 branch from 02a685a to 7816c35 Compare December 28, 2024 19:33
include:
- { rubocop: master, ruby: "3.0", os: ubuntu }
- { rubocop: "v1.61.0", ruby: "3.3", os: ubuntu }
- { rubocop: "v1.69.2", ruby: "3.4", os: ubuntu }
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess, this is supposed to test that rubocop-ast still works with older rubocop? Would it then make more sense to instead test master against the latest ruby version so that this can be left with and older version?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have strong opinions about this, this PR aligns with the previous upgrade:
#274

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can open a followup

@koic koic merged commit fae4cbe into rubocop:master Dec 28, 2024
@koic koic deleted the ci_against_ruby_34 branch December 28, 2024 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants