rubocop-lts-rspec 1.0.3 → 1.0.4

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 CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 62310645a199da8e1b8c80c7b6fa0d338d76ced0b474f68323fea9d7ff05a52c
4
- data.tar.gz: 254492f04575635b01ee648f04ef7c3677983133661bcaad68684acb0e1807d6
3
+ metadata.gz: 15c117e508905f1abf09e416c6001c2305de106053d79e9557d00faaf891fc33
4
+ data.tar.gz: 20132f1c07852eda304a8095067f23fa8d5f1071928ec9ee685c1b8570fb673c
5
5
  SHA512:
6
- metadata.gz: ca0e9e4d778ca8e3ba56968afb957d2474a5b8e20e7887e5d4ff4469cd03cdde1bd0be799aaae20bb5255afeeb0f828de21c3d2d0659ee0523c42fb3269c296b
7
- data.tar.gz: 96a47f9828ebb7964c0227d6a529fee658e58441f39238bc639dc838151bbd9db806e15108e60b3ce15aa19a171794a4687ee3cc6f510c8753212aff5d29874d
6
+ metadata.gz: 5156d662c4217080d7ba519e544fbc47c8cd1f176f69e934596bf04b4dc29d50d91b739007d843d9f534d415488f0a12b2e6ae8583b4aefe155410bbdf73dc82
7
+ data.tar.gz: 8a221258e7f0c9119741717488dd9914ea12a7f261efc5e72c2c285b12411008f86e078bea36c4cf7bb581b25bcb058c7978ef6697ef3c7b228baba8dae0497f
checksums.yaml.gz.sig CHANGED
Binary file
data/.rubocop.yml ADDED
@@ -0,0 +1,46 @@
1
+ inherit_gem:
2
+ rubocop-lts: rubocop-lts.yml
3
+
4
+ # Metrics cops are disabled in Standard by default
5
+ Metrics:
6
+ Enabled: true
7
+
8
+ # Ruby specific customizations
9
+ Layout/LineLength:
10
+ Max: 120
11
+
12
+ Style/HashSyntax:
13
+ EnforcedStyle: ruby19_no_mixed_keys
14
+
15
+ Style/TrailingCommaInArrayLiteral:
16
+ EnforcedStyleForMultiline: consistent_comma
17
+ Enabled: true
18
+ inherit_from:
19
+ - .rubocop_rspec.yml
20
+ plugins:
21
+ - rubocop-on-rbs
22
+ - rubocop-packaging
23
+ # This tells RuboCop to add the exclusions in this file
24
+ # to the default exclusions (and those from other inherited files),
25
+ # rather than overwriting them.
26
+ inherit_mode:
27
+ merge:
28
+ - Exclude
29
+ AllCops:
30
+ Exclude:
31
+ - certs/**/*
32
+ - checksums/**/*
33
+ - docs/**/*
34
+ - examples/**/*
35
+ - fixtures/**/*
36
+ - gemfiles/*.gemfile
37
+ - pkg/**/*
38
+ - results/**/*
39
+ - spec/fixtures/**/*
40
+ - tmp/**/*
41
+ - vendor/**/*
42
+ - AGENTS.md
43
+ RBS:
44
+ Enabled: true
45
+ Layout/IndentationConsistency:
46
+ Exclude: ['*.md']
data/CHANGELOG.md CHANGED
@@ -1,18 +1,63 @@
1
1
  # Changelog
2
+
3
+ [![SemVer 2.0.0][📌semver-img]][📌semver] [![Keep-A-Changelog 1.0.0][📗keep-changelog-img]][📗keep-changelog]
4
+
2
5
  All notable changes to this project will be documented in this file.
3
6
 
4
- The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
5
- and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
+ The format is based on [Keep a Changelog][📗keep-changelog],
8
+ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
9
+ and [yes][📌major-versions-not-sacred], platform and engine support are part of the [public API][📌semver-breaking].
10
+ Please file a bug if you notice a violation of semantic versioning.
11
+
12
+ [📌semver]: https://semver.org/spec/v2.0.0.html
13
+ [📌semver-img]: https://img.shields.io/badge/semver-2.0.0-FFDD67.svg?style=flat
14
+ [📌semver-breaking]: https://github.com/semver/semver/issues/716#issuecomment-869336139
15
+ [📌major-versions-not-sacred]: https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
16
+ [📗keep-changelog]: https://keepachangelog.com/en/1.0.0/
17
+ [📗keep-changelog-img]: https://img.shields.io/badge/keep--a--changelog-1.0.0-FFDD67.svg?style=flat
6
18
 
7
19
  ## [Unreleased]
20
+
8
21
  ### Added
22
+
9
23
  ### Changed
10
- ### Fixed
24
+
25
+ ### Deprecated
26
+
11
27
  ### Removed
12
28
 
29
+ ### Fixed
30
+
31
+ ### Security
32
+
33
+ ## [1.0.4] - 2026-06-28
34
+
35
+ - TAG: [v1.0.4][1.0.4t]
36
+ - COVERAGE: 100.00% -- 16/16 lines in 3 files
37
+ - BRANCH COVERAGE: 0.00% -- 0/0 branches in 3 files
38
+ - 57.14% documented
39
+
40
+ ### Added
41
+
42
+ - Added support for JRuby 10.1 and TruffleRuby 34.0.
43
+
44
+ ### Changed
45
+
46
+ - Retemplated project metadata and CI/development automation with `kettle-jem` v7.0.0.
47
+
48
+ ### Fixed
49
+
50
+ - Restored the destination `spec.files` package declaration so the built gem
51
+ includes its `config/**/*.yml` RuboCop configuration files.
52
+ - Restored `docs/CNAME` so the generated documentation site keeps its custom domain.
53
+ - Corrected misspelled contact metadata to use `galtzo.com`.
54
+
13
55
  ## [1.0.3] 2026-06-01
56
+
14
57
  ### Added
58
+
15
59
  ### Changed
60
+
16
61
  - Updated dependency floors:
17
62
  - `rubocop` to `~> 1.84`, `>= 1.84.2`.
18
63
  - `rubocop-factory_bot` to `~> 2.28`, `>= 2.28.0`.
@@ -22,30 +67,51 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
22
67
  - `standard-rspec` to `~> 0.5`, `>= 0.5.0`.
23
68
  - Release and test dependencies to their latest compatible floors.
24
69
  - Corrected gem metadata to declare the Ruby 3.2 runtime floor that has been implicit since the last major release.
70
+
25
71
  ### Fixed
72
+
26
73
  ### Removed
27
74
 
28
75
  ## [1.0.2] 2026-06-01
76
+
29
77
  ### Added
78
+
30
79
  ### Changed
80
+
31
81
  - Load RSpec-family RuboCop extensions through RuboCop's plugin API.
82
+
32
83
  ### Fixed
84
+
33
85
  ### Removed
34
86
 
35
87
  ## [1.0.1] 2026-05-30
88
+
36
89
  ### Added
90
+
37
91
  - Coverage dependency for release specs.
92
+
38
93
  ### Changed
94
+
39
95
  - Updated release and documentation dependencies.
96
+
40
97
  ### Fixed
98
+
41
99
  ### Removed
100
+
42
101
  - rubocop-shopify as a transitive dependency (via rubocop-lts)
43
102
 
44
103
  ## [1.0.0] 2023-04-16
104
+
45
105
  - Initial release
46
106
 
47
- [Unreleased]: https://gitlab.com/rubocop-lts/rubocop-lts-rspec/-/compare/v1.0.3...HEAD
48
- [1.0.0]: https://gitlab.com/rubocop-lts/rubocop-lts-rspec/-/compare/436f8d55bd1f60cf4be17f5cd57021cd3c49a4da...v1.0.0
107
+ [Unreleased]: https://github.com/rubocop-lts/rubocop-lts-rspec/compare/v1.0.4...HEAD
108
+ [1.0.6]: https://github.com/rubocop-lts/rubocop-lts-rspec/compare/v1.0.5...v1.0.6
109
+ [1.0.6t]: https://github.com/rubocop-lts/rubocop-lts-rspec/releases/tag/v1.0.6
110
+ [1.0.5]: https://github.com/rubocop-lts/rubocop-lts-rspec/compare/v1.0.3...v1.0.5
111
+ [1.0.5t]: https://github.com/rubocop-lts/rubocop-lts-rspec/releases/tag/v1.0.5
112
+ [1.0.4]: https://github.com/rubocop-lts/rubocop-lts-rspec/compare/v1.0.3...v1.0.4
113
+ [1.0.4t]: https://github.com/rubocop-lts/rubocop-lts-rspec/releases/tag/v1.0.4
114
+ [1.0.3]: https://gitlab.com/rubocop-lts/rubocop-lts-rspec/-/compare/v1.0.2...v1.0.3
49
115
  [1.0.2]: https://gitlab.com/rubocop-lts/rubocop-lts-rspec/-/compare/v1.0.1...v1.0.2
50
116
  [1.0.1]: https://gitlab.com/rubocop-lts/rubocop-lts-rspec/-/compare/v1.0.0...v1.0.1
51
- [1.0.3]: https://gitlab.com/rubocop-lts/rubocop-lts-rspec/-/compare/v1.0.2...v1.0.3
117
+ [1.0.0]: https://github.com/rubocop-lts/rubocop-lts-rspec/compare/436f8d55bd1f60cf4be17f5cd57021cd3c49a4da...v1.0.0
data/CITATION.cff ADDED
@@ -0,0 +1,20 @@
1
+ cff-version: 1.2.0
2
+ title: "rubocop-lts-rspec"
3
+ message: >-
4
+ If you use this work and you want to cite it,
5
+ then you can use the metadata from this file.
6
+ type: software
7
+ authors:
8
+ - given-names: "Peter H."
9
+ family-names: "Boling"
10
+ email: "floss@galtzo.com"
11
+ affiliation: "galtzo.com"
12
+ orcid: 'https://orcid.org/0009-0008-8519-441X'
13
+ identifiers:
14
+ - type: url
15
+ value: 'https://github.com/rubocop-lts/rubocop-lts-rspec'
16
+ description: "rubocop-lts-rspec"
17
+ repository-code: 'https://github.com/rubocop-lts/rubocop-lts-rspec'
18
+ abstract: >-
19
+ rubocop-lts-rspec
20
+ license: See license file
data/CODE_OF_CONDUCT.md CHANGED
@@ -2,83 +2,133 @@
2
2
 
3
3
  ## Our Pledge
4
4
 
5
- We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
5
+ We as members, contributors, and leaders pledge to make participation in our
6
+ community a harassment-free experience for everyone, regardless of age, body
7
+ size, visible or invisible disability, ethnicity, sex characteristics, gender
8
+ identity and expression, level of experience, education, socio-economic status,
9
+ nationality, personal appearance, race, caste, color, religion, or sexual
10
+ identity and orientation.
6
11
 
7
- We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
12
+ We pledge to act and interact in ways that contribute to an open, welcoming,
13
+ diverse, inclusive, and healthy community.
8
14
 
9
15
  ## Our Standards
10
16
 
11
- Examples of behavior that contributes to a positive environment for our community include:
17
+ Examples of behavior that contributes to a positive environment for our
18
+ community include:
12
19
 
13
20
  * Demonstrating empathy and kindness toward other people
14
21
  * Being respectful of differing opinions, viewpoints, and experiences
15
22
  * Giving and gracefully accepting constructive feedback
16
- * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
17
- * Focusing on what is best not just for us as individuals, but for the overall community
23
+ * Accepting responsibility and apologizing to those affected by our mistakes,
24
+ and learning from the experience
25
+ * Focusing on what is best not just for us as individuals, but for the overall
26
+ community
18
27
 
19
28
  Examples of unacceptable behavior include:
20
29
 
21
- * The use of sexualized language or imagery, and sexual attention or
22
- advances of any kind
30
+ * The use of sexualized language or imagery, and sexual attention or advances of
31
+ any kind
23
32
  * Trolling, insulting or derogatory comments, and personal or political attacks
24
33
  * Public or private harassment
25
- * Publishing others' private information, such as a physical or email
26
- address, without their explicit permission
34
+ * Publishing others' private information, such as a physical or email address,
35
+ without their explicit permission
27
36
  * Other conduct which could reasonably be considered inappropriate in a
28
37
  professional setting
29
38
 
30
39
  ## Enforcement Responsibilities
31
40
 
32
- Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
41
+ Community leaders are responsible for clarifying and enforcing our standards of
42
+ acceptable behavior and will take appropriate and fair corrective action in
43
+ response to any behavior that they deem inappropriate, threatening, offensive,
44
+ or harmful.
33
45
 
34
- Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
46
+ Community leaders have the right and responsibility to remove, edit, or reject
47
+ comments, commits, code, wiki edits, issues, and other contributions that are
48
+ not aligned to this Code of Conduct, and will communicate reasons for moderation
49
+ decisions when appropriate.
35
50
 
36
51
  ## Scope
37
52
 
38
- This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
53
+ This Code of Conduct applies within all community spaces, and also applies when
54
+ an individual is officially representing the community in public spaces.
55
+ Examples of representing our community include using an official email address,
56
+ posting via an official social media account, or acting as an appointed
57
+ representative at an online or offline event.
39
58
 
40
59
  ## Enforcement
41
60
 
42
- Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at peter.boling@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
61
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
62
+ reported to the community leaders responsible for enforcement at
63
+ [![Contact Maintainer][🚂maint-contact-img]][🚂maint-contact].
64
+ All complaints will be reviewed and investigated promptly and fairly.
43
65
 
44
- All community leaders are obligated to respect the privacy and security of the reporter of any incident.
66
+ All community leaders are obligated to respect the privacy and security of the
67
+ reporter of any incident.
45
68
 
46
69
  ## Enforcement Guidelines
47
70
 
48
- Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
71
+ Community leaders will follow these Community Impact Guidelines in determining
72
+ the consequences for any action they deem in violation of this Code of Conduct:
49
73
 
50
74
  ### 1. Correction
51
75
 
52
- **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
76
+ **Community Impact**: Use of inappropriate language or other behavior deemed
77
+ unprofessional or unwelcome in the community.
53
78
 
54
- **Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
79
+ **Consequence**: A private, written warning from community leaders, providing
80
+ clarity around the nature of the violation and an explanation of why the
81
+ behavior was inappropriate. A public apology may be requested.
55
82
 
56
83
  ### 2. Warning
57
84
 
58
- **Community Impact**: A violation through a single incident or series of actions.
85
+ **Community Impact**: A violation through a single incident or series of
86
+ actions.
59
87
 
60
- **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
88
+ **Consequence**: A warning with consequences for continued behavior. No
89
+ interaction with the people involved, including unsolicited interaction with
90
+ those enforcing the Code of Conduct, for a specified period of time. This
91
+ includes avoiding interactions in community spaces as well as external channels
92
+ like social media. Violating these terms may lead to a temporary or permanent
93
+ ban.
61
94
 
62
95
  ### 3. Temporary Ban
63
96
 
64
- **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
97
+ **Community Impact**: A serious violation of community standards, including
98
+ sustained inappropriate behavior.
65
99
 
66
- **Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
100
+ **Consequence**: A temporary ban from any sort of interaction or public
101
+ communication with the community for a specified period of time. No public or
102
+ private interaction with the people involved, including unsolicited interaction
103
+ with those enforcing the Code of Conduct, is allowed during this period.
104
+ Violating these terms may lead to a permanent ban.
67
105
 
68
106
  ### 4. Permanent Ban
69
107
 
70
- **Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
108
+ **Community Impact**: Demonstrating a pattern of violation of community
109
+ standards, including sustained inappropriate behavior, harassment of an
110
+ individual, or aggression toward or disparagement of classes of individuals.
71
111
 
72
- **Consequence**: A permanent ban from any sort of public interaction within the community.
112
+ **Consequence**: A permanent ban from any sort of public interaction within the
113
+ community.
73
114
 
74
115
  ## Attribution
75
116
 
76
- This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
77
- available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
117
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118
+ version 2.1, available at
119
+ [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
78
120
 
79
- Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
80
-
81
- [homepage]: https://www.contributor-covenant.org
121
+ Community Impact Guidelines were inspired by
122
+ [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
82
123
 
83
124
  For answers to common questions about this code of conduct, see the FAQ at
84
- https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
125
+ [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126
+ [https://www.contributor-covenant.org/translations][translations].
127
+
128
+ [homepage]: https://www.contributor-covenant.org
129
+ [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130
+ [Mozilla CoC]: https://github.com/mozilla/diversity
131
+ [FAQ]: https://www.contributor-covenant.org/faq
132
+ [translations]: https://www.contributor-covenant.org/translations
133
+ [🚂maint-contact]: http://www.railsbling.com/contact
134
+ [🚂maint-contact-img]: https://img.shields.io/badge/Contact-Maintainer-0093D0.svg?style=flat&logo=rubyonrails&logoColor=red