rubocop-ruby2_7 1.1.1 → 1.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c578c1d05c141d9c4379bc7b36afdda7f31f8aa75b59be6aea316d9eef0b15aa
-  data.tar.gz: e1b1e5d51b8bed8006df03ffcb77500d75d467ecdef19b769268533ae1fffb5d
+  metadata.gz: 9ea339dc8616b27a1bde52a824acada79ad7a95577910de226806103639d3831
+  data.tar.gz: 1aba43f9aea519043f1cafd116961ac6d343ee688328fbcfd85c72557de6b566
 SHA512:
-  metadata.gz: 8fbf80c4f8b75b354a018b151e779346abc0433a5a2f5d2ca6897398fa833d0fd40b766d4e50e5d81daba2ac1f8c77f2a3b1a2059c5b2b24c50f893f64d96262
-  data.tar.gz: b3e39294096bb15240f4283e61587cd28a1078aea678994cb57d960a8810dab8e1319d01e0e7554f8f310a6d24778d7d2cfd9a3ec8a9578ddc76de36418c1906
+  metadata.gz: da213804037c9003f0230a6f07d70296f86e382b3cf874f8595b6e3ace4574cbabb2baa305c7e703723daeb5f481a58e3e4dd7d0a35ba4eda1547a0612614124
+  data.tar.gz: 961f5c4a3258f3f10ac6067f181b29585a38e1c5902f48097ca84ae9d28da95591f566a4d7922889aa1474d89eb264dc0b15ecea1445e1251410225827f8e2c1

data/CHANGELOG.md

@@ -10,6 +10,15 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Fixed
 ### Removed
 
+## [1.1.2] 2023-02-01
+### Fixed
+* Stop defining global variable in version.rb
+### Changed
+* Upgraded to RuboCop v1.44.1
+  * Compatible with rubocop-packaging ~> 0.5.2
+* Improved development documentation
+* Improved documentation on SemVer adherence
+
 ## [1.1.1] 2022-12-20
 ### Fixed
 * Documentation of Three Guarantees:
@@ -60,7 +69,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Added
 * Initial release
 
-[Unreleased]: https://github.com/rubocop-lts/rubocop-ruby2_7/compare/v1.1.1...HEAD
+[Unreleased]: https://github.com/rubocop-lts/rubocop-ruby2_7/compare/v1.1.2...HEAD
+[1.1.2]: https://github.com/rubocop-lts/rubocop-ruby2_7/compare/v1.1.1...v1.1.2
 [1.1.1]: https://github.com/rubocop-lts/rubocop-ruby2_7/compare/v1.1.0...v1.1.1
 [1.1.0]: https://github.com/rubocop-lts/rubocop-ruby2_7/compare/v1.0.6...v1.1.0
 [1.0.6]: https://github.com/rubocop-lts/rubocop-ruby2_7/compare/v1.0.5...v1.0.6

data/CONTRIBUTING.md

@@ -11,13 +11,14 @@ and post a message to the [gitter chat][🏘chat].
 
 To release a new version:
 
-1. update the version number in `version.rb`
-2. run `bundle exec rake build:checksum`
-3. move the built gem to project root
-4. run `bin/checksum` to create the missing SHA256 checksum
-5. move the built gem back to `pkg/`
-6. commit the changes
-7. run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org][rubygems].
+1. Run `bin/setup && bin/rake` as a tests, coverage, & linting sanity check.
+2. update the version number in `version.rb`
+3. run `bundle exec rake build:checksum`
+4. move the built gem to project root
+5. run `bin/checksum` to create the missing SHA256 checksum
+6. move the built gem back to `pkg/`
+7. commit the changes
+8. run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org][rubygems].
 
 NOTE: You will need to have a public key in `certs/`, and list your cert in the
 `gemspec`, in order to sign the new release.

data/README.md

@@ -86,10 +86,14 @@ This gem requires no other gems. It depends on `rubocop`, but does not `require
 
 Awareness of `rubocop`'s lack of [SemVer][semver] adherence isn't evenly dispersed in the Ruby community.
 
-The RuboCop team [has real reasons](https://github.com/semver/semver/issues/317)
-for [not following SemVer](https://github.com/rubocop/rubocop/issues/4243), but if you've
-found this project their reasons likely weigh less, in your context (e.g. running `rubocop` from command line), than
-what brought you here.
+The RuboCop team [has reasons](https://github.com/semver/semver/issues/317)
+for [not following SemVer](https://github.com/rubocop/rubocop/issues/4243).
+
+NOTE: They think they are following SemVer,
+but their interpretation differs from mine, and seems to differ from the
+[intent of SemVer's creator][major-versions-not-sacred].
+
+If you need to run `rubocop` from command line in an older version of Ruby, you've come to the right place.
 
 <p align="left">
     <a href="https://metaredux.com/posts/2022/04/21/rubocop-turns-10.html" target="_blank" rel="noopener">
@@ -98,26 +102,39 @@ what brought you here.
 </p>
 
 The purpose of this gem is to constrain the `rubocop` dependency of a project in
-a [SemVer compliant](https://semver.org/) (Semantic Versioning) way that aligns with the the desired minimum
-compatible/supported Ruby version.
+a [SemVer compliant][semver]
+(Semantic Versioning, [Major Versions are Not Sacred][major-versions-not-sacred])
+way that aligns with the the desired minimum compatible/supported Ruby version.
 
 ## Ruby Version Support
 
 Adding this gem will facilitate the best practice of adding a `~> ` version constrained `rubocop` dependency, while
 minimizing the risk of a rubocop minor / patch upgrade breaking the build. See the
-official [compatibility matrix][rubocop-matrix] for `rubocop`.
+official [compatibility matrix][rubocop-support-matrix] for `rubocop`.
 
 ### Three Guarantees
 
-`rubocop-ruby3_0` (this gem) will install a version of `rubocop` which will
+This gem will install a version of `rubocop` which will
 **install** on (1), **run** on (2), and **analyze code** (3) intended to support any version of Ruby >= 2.7.
 
 Any change to any of those three abilities would require a major version bump.
-Each [spring `rubocop` drops][rubocop-matrix] the ability to **install** and **run** `rubocop` on an EOL'd Ruby.
+Each [spring `rubocop` drops][rubocop-support-matrix] the ability to **install** and **run** `rubocop` on an EOL'd Ruby.
 Eventually `rubocop` will drop the ability to **analyze code** intended to support an EOL'd Ruby,
 as they already have for Ruby 1.8 and 1.9.
-When the `rubocop` team makes any of these changes they typically only bump the minor version of ruby,
-in violation of SemVer.  This is a primary _raison d’être_ for this project.
+When the `rubocop` team makes _any_ of these changes they
+[only bump the minor version][rubocop-versioning] of RuboCop,
+in violation of SemVer ([they disagree][rubocop-release-policy]).
+In other words, RuboCop intentionally does not bump the major version when they drop
+_analysis_, _runtime_, or _installation_ support for a given version of Ruby.
+This is a primary _raison d’être_ for this project.
+To get a better understanding of how SemVer is intended to work read this article from the creator of SemVer:
+
+- ["Major Version Numbers are Not Sacred"][major-versions-not-sacred]
+
+[rubocop-support-matrix]: https://docs.rubocop.org/rubocop/compatibility.html#support-matrix
+[rubocop-versioning]: https://docs.rubocop.org/rubocop/versioning.html
+[rubocop-release-policy]: https://docs.rubocop.org/rubocop/versioning.html#release-policy
+[major-versions-not-sacred]: https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
 
 ### A Gem Family
 
@@ -149,7 +166,6 @@ They can be used as development dependencies for libraries or applications.
 [rr30]: https://gitlab.com/rubocop-lts/rubocop-ruby3_0
 [rr31]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1
 [what1_8]: https://gitlab.com/rubocop-lts/rubocop-ruby1_9#what-about-ruby-18
-[rubocop-matrix]: https://github.com/rubocop/rubocop/blob/master/docs/modules/ROOT/pages/compatibility.adoc#support-matrix
 
 ## 🗿 Stable
 
@@ -203,7 +219,10 @@ But this gem shoehorns rubocop into SemVer... so `NewCops` is now safe(r)!  If y
 
 ## Development
 
-After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+After checking out the repo, run `bin/setup` to install dependencies.
+Then, run `rake spec` to run the tests w/ coverage,
+or `bin/rake` to run tests w/ coverage, and linting.
+You can also run `bin/console` for an interactive prompt that will allow you to experiment.
 
 To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
 
@@ -244,7 +263,7 @@ License: [Unsplash License][org-logo-license]
 
 ### © Copyright
 
-* Copyright (c) 2022 [Peter H. Boling][peterboling] of [Rails Bling][railsbling]
+* Copyright (c) 2022 - 2023 [Peter H. Boling][peterboling] of [Rails Bling][railsbling]
 
 [copyright-notice-explainer]: https://opensource.stackexchange.com/questions/5778/why-do-licenses-such-as-the-mit-license-specify-a-single-year
 
@@ -300,8 +319,6 @@ spec.add_dependency "rubocop-ruby2_7", "~> 1.1"
 
 [tweetme]: http://twitter.com/galtzo
 
-[politicme]: https://nationalprogressiveparty.org
-
 [documentation]: https://rubydoc.info/github/rubocop-lts/rubocop-ruby2_7/main
 
 [source]: https://github.com/rubocop-lts/rubocop-ruby2_7/

data/lib/rubocop/ruby2_7/version.rb

@@ -2,6 +2,6 @@
 
 module Rubocop
   module Ruby27
-    VERSION = "1.1.1"
+    VERSION = "1.1.2"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rubocop-ruby2_7
 version: !ruby/object:Gem::Version
-  version: 1.1.1
+  version: 1.1.2
 platform: ruby
 authors:
 - Peter Boling
@@ -36,7 +36,7 @@ cert_chain:
   gwGrEXGQGDZ0NIgBcmvMOqlXjkGQwQvugKycJ024z89+fz2332vdZIKTrSxJrXGk
   4/bR9A==
   -----END CERTIFICATE-----
-date: 2022-12-20 00:00:00.000000000 Z
+date: 2023-02-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rubocop
@@ -44,14 +44,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.40.0
+        version: 1.44.1
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.40.0
+        version: 1.44.1
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
@@ -84,16 +84,16 @@ dependencies:
   name: yard
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '0.9'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '0.9'
 description: Links dependency on minimum Ruby version to maximum RuboCop version
 email:
 - peter.boling@gmail.com
@@ -116,10 +116,10 @@ licenses:
 - MIT
 metadata:
   homepage_uri: https://github.com/rubocop-lts/rubocop-ruby2_7
-  source_code_uri: https://github.com/rubocop-lts/rubocop-ruby2_7/tree/v1.1.1
-  changelog_uri: https://github.com/rubocop-lts/rubocop-ruby2_7/blob/v1.1.1/CHANGELOG.md
+  source_code_uri: https://github.com/rubocop-lts/rubocop-ruby2_7/tree/v1.1.2
+  changelog_uri: https://github.com/rubocop-lts/rubocop-ruby2_7/blob/v1.1.2/CHANGELOG.md
   bug_tracker_uri: https://github.com/rubocop-lts/rubocop-ruby2_7/issues
-  documentation_uri: https://www.rubydoc.info/gems/rubocop-ruby2_7/1.1.1
+  documentation_uri: https://www.rubydoc.info/gems/rubocop-ruby2_7/1.1.2
   funding_uri: https://liberapay.com/pboling
   wiki_uri: https://github.com/rubocop-lts/rubocop-ruby2_7/wiki
   rubygems_mfa_required: 'true'
@@ -138,7 +138,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.6
+rubygems_version: 3.4.4
 signing_key:
 specification_version: 4
 summary: Semantically Versioned RuboCop Dependency