makandra-rubocop 17.0.0 → 18.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/.ruby-version +1 -1
- data/CHANGELOG.md +15 -0
- data/Gemfile.lock +24 -18
- data/README.md +14 -5
- data/config/default.yml +605 -159
- data/config/ext/capybara.yml +132 -51
- data/config/ext/factory_bot.yml +8 -8
- data/config/ext/minitest.yml +358 -0
- data/config/ext/rails.yml +41 -26
- data/config/ext/rspec.yml +27 -1
- data/config/ext/rspec_rails.yml +21 -8
- data/lib/makandra_rubocop/version.rb +1 -1
- data/makandra-rubocop.gemspec +6 -5
- metadata +28 -16
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 110ef940c3428917aeb69fa5c4013db21d0d7b845258d842c0fcf5a434bf05dc
|
|
4
|
+
data.tar.gz: 494578dcefaf0183d1294d1e32e67afaba645e4c70aff6440ffcf5b28ed872d7
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: afa9bee462ce0bae2a501971c93caecdd20acb879c4ccada8f37fe7fac7fe290b271f986b1a74f5874b667d94e15827f4c1cc3407bfaa367b8e39c0ff51f0e6b
|
|
7
|
+
data.tar.gz: 0c3165af8b57b2697b5bd4a1b5ab882c664729e58fbb34d8f34696d3176fa9dd05a3eee2a7299b53af3291823de7c2431ae126c75772bf407590f68b3e14d1f4
|
data/.ruby-version
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
|
|
1
|
+
3.4.8
|
data/CHANGELOG.md
CHANGED
|
@@ -8,6 +8,21 @@ This project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html
|
|
|
8
8
|
|
|
9
9
|
### Compatible changes
|
|
10
10
|
|
|
11
|
+
## 18.0.0 - 2026-10-19
|
|
12
|
+
|
|
13
|
+
### Breaking changes
|
|
14
|
+
- Upgrade rubocop from 1.84.1 to 1.92.0
|
|
15
|
+
- Upgrade rubocop-capybara from 2.22.1 to 3.1.0
|
|
16
|
+
- `Capybara/ClickLinkOrButtonStyle` was removed upstream
|
|
17
|
+
- Matcher cops moved into the `Capybara/RSpec` department, which is now enabled. This also enables `Capybara/RSpec/HaveSelector` and `Capybara/RSpec/PredicateMatcher`, which upstream enabled in 3.0.
|
|
18
|
+
- Upgrade rubocop-rails from 2.34.3 to 2.38.0
|
|
19
|
+
- Upgrade rubocop-rspec from 3.9.0 to 3.10.2
|
|
20
|
+
- Upgrade rubocop-rspec_rails from 2.32.0 to 2.33.0
|
|
21
|
+
|
|
22
|
+
### Compatible changes
|
|
23
|
+
- Add `rubocop-minitest` 0.41.0 with `config/ext/minitest.yml`
|
|
24
|
+
- Set `NewCops: disable`, so new (`pending`) cops stay disabled until we explicitly enable them. All cops that were `pending` before this release are now `Enabled: true` and keep running as before. The `pending` cops added by the upgrades above are disabled.
|
|
25
|
+
|
|
11
26
|
## 17.0.0 - 2026-02-10
|
|
12
27
|
|
|
13
28
|
## Breaking changes
|
data/Gemfile.lock
CHANGED
|
@@ -1,13 +1,14 @@
|
|
|
1
1
|
PATH
|
|
2
2
|
remote: .
|
|
3
3
|
specs:
|
|
4
|
-
makandra-rubocop (
|
|
5
|
-
rubocop (~> 1.
|
|
6
|
-
rubocop-capybara (~>
|
|
4
|
+
makandra-rubocop (18.0.0)
|
|
5
|
+
rubocop (~> 1.92.0)
|
|
6
|
+
rubocop-capybara (~> 3.1.0)
|
|
7
7
|
rubocop-factory_bot (~> 2.28.0)
|
|
8
|
-
rubocop-
|
|
9
|
-
rubocop-
|
|
10
|
-
rubocop-
|
|
8
|
+
rubocop-minitest (~> 0.41.0)
|
|
9
|
+
rubocop-rails (~> 2.38.0)
|
|
10
|
+
rubocop-rspec (~> 3.10.2)
|
|
11
|
+
rubocop-rspec_rails (~> 2.33.0)
|
|
11
12
|
|
|
12
13
|
GEM
|
|
13
14
|
remote: https://rubygems.org/
|
|
@@ -50,38 +51,43 @@ GEM
|
|
|
50
51
|
rainbow (3.1.1)
|
|
51
52
|
rake (12.3.2)
|
|
52
53
|
regexp_parser (2.11.3)
|
|
53
|
-
rubocop (1.
|
|
54
|
-
json (
|
|
54
|
+
rubocop (1.92.0)
|
|
55
|
+
json (>= 2.3)
|
|
55
56
|
language_server-protocol (~> 3.17.0.2)
|
|
56
57
|
lint_roller (~> 1.1.0)
|
|
57
|
-
parallel (
|
|
58
|
+
parallel (>= 1.10)
|
|
58
59
|
parser (>= 3.3.0.2)
|
|
59
60
|
rainbow (>= 2.2.2, < 4.0)
|
|
60
|
-
regexp_parser (>= 2.
|
|
61
|
+
regexp_parser (>= 2.11.3, < 3.0)
|
|
61
62
|
rubocop-ast (>= 1.49.0, < 2.0)
|
|
62
63
|
ruby-progressbar (~> 1.7)
|
|
63
64
|
unicode-display_width (>= 2.4.0, < 4.0)
|
|
64
65
|
rubocop-ast (1.49.0)
|
|
65
66
|
parser (>= 3.3.7.2)
|
|
66
67
|
prism (~> 1.7)
|
|
67
|
-
rubocop-capybara (
|
|
68
|
+
rubocop-capybara (3.1.0)
|
|
68
69
|
lint_roller (~> 1.1)
|
|
69
|
-
rubocop (~> 1.
|
|
70
|
+
rubocop (~> 1.89)
|
|
70
71
|
rubocop-factory_bot (2.28.0)
|
|
71
72
|
lint_roller (~> 1.1)
|
|
72
73
|
rubocop (~> 1.72, >= 1.72.1)
|
|
73
|
-
rubocop-
|
|
74
|
+
rubocop-minitest (0.41.0)
|
|
75
|
+
lint_roller (~> 1.1)
|
|
76
|
+
rubocop (>= 1.89.0, < 2.0)
|
|
77
|
+
rubocop-ast (>= 1.38.0, < 2.0)
|
|
78
|
+
rubocop-rails (2.38.0)
|
|
74
79
|
activesupport (>= 4.2.0)
|
|
75
80
|
lint_roller (~> 1.1)
|
|
76
81
|
rack (>= 1.1)
|
|
77
|
-
rubocop (>= 1.
|
|
82
|
+
rubocop (>= 1.89.0, < 2.0)
|
|
78
83
|
rubocop-ast (>= 1.44.0, < 2.0)
|
|
79
|
-
rubocop-rspec (3.
|
|
84
|
+
rubocop-rspec (3.10.2)
|
|
80
85
|
lint_roller (~> 1.1)
|
|
81
|
-
|
|
82
|
-
|
|
86
|
+
regexp_parser (>= 2.0)
|
|
87
|
+
rubocop (~> 1.86, >= 1.86.2)
|
|
88
|
+
rubocop-rspec_rails (2.33.0)
|
|
83
89
|
lint_roller (~> 1.1)
|
|
84
|
-
rubocop (~> 1.
|
|
90
|
+
rubocop (~> 1.89)
|
|
85
91
|
rubocop-rspec (~> 3.5)
|
|
86
92
|
ruby-progressbar (1.13.0)
|
|
87
93
|
securerandom (0.3.2)
|
data/README.md
CHANGED
|
@@ -84,6 +84,15 @@ inherit_gem:
|
|
|
84
84
|
- config/ext/factory_bot.yml
|
|
85
85
|
```
|
|
86
86
|
|
|
87
|
+
**For Minitest**
|
|
88
|
+
|
|
89
|
+
```yaml
|
|
90
|
+
inherit_gem:
|
|
91
|
+
makandra-rubocop:
|
|
92
|
+
- config/default.yml
|
|
93
|
+
- config/ext/minitest.yml
|
|
94
|
+
```
|
|
95
|
+
|
|
87
96
|
Any per-project rules can then be defined in the `.rubocop.yml`:
|
|
88
97
|
|
|
89
98
|
```yaml
|
|
@@ -167,8 +176,8 @@ For release run `bundle exec rake release`, which will create a git tag for the
|
|
|
167
176
|
version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
|
|
168
177
|
|
|
169
178
|
### Upgrading Rubocop dependencies
|
|
170
|
-
The following procedure works for
|
|
171
|
-
`
|
|
179
|
+
The following procedure works for `rubocop` and each of its plugins (`rubocop-rails`,
|
|
180
|
+
`rubocop-rspec`, `rubocop-minitest`, ...). (Replace `rubocop` with the respective dependency name.)
|
|
172
181
|
|
|
173
182
|
1. Change the `rubocop` dependency in the Gemspec to the version you want to
|
|
174
183
|
upgrade to.
|
|
@@ -184,9 +193,9 @@ you have not added the Rubocop remote yet (check with `git remote -v`), do a
|
|
|
184
193
|
Gemspec. The easiest way is to look them up on their [releases page](https://github.com/rubocop/rubocop/releases).
|
|
185
194
|
3. Diff their config/default.yml between the previously used and the new Rubocop
|
|
186
195
|
version, and write it to a file: `git diff $OLDER_SHA $NEWER_SHA config/default.yml > config_diff`
|
|
187
|
-
4. If you are updating `rubocop-rails` or `rubocop-rspec`, edit the config_diff
|
|
188
|
-
file now and replace `config/default.yml` with `config/ext
|
|
189
|
-
(
|
|
196
|
+
4. If you are updating a plugin like `rubocop-rails` or `rubocop-rspec`, edit the config_diff
|
|
197
|
+
file now and replace `config/default.yml` with the plugin's file in `config/ext/`
|
|
198
|
+
(e.g. `config/ext/rails.yml`).
|
|
190
199
|
5. Apply the diff with `git apply ./config_diff --3way`
|
|
191
200
|
6. Resolve merge conflicts carefully and review all changes. We do not want to
|
|
192
201
|
loose changes in [our config files](https://github.com/makandra/makandra-rubocop/tree/master/config).
|