rubocop-ruby3_0 1.1.0 → 1.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4e3371a4053ba36a1e7036bea52e94c2de373c6c0222d992d45fdfe025b20c01
-  data.tar.gz: 6f238448e57589b20b64ba06e62232d50688222a273c6d8c9f11872310664257
+  metadata.gz: 217dd141a2b56af2db16cc695a4ff686a24dd489e1f1ebdb65f5c3faa753be15
+  data.tar.gz: cc5dd03f6ac71b46ea148123b64fce098afd0ae4573cecc9096e96cc22ea5714
 SHA512:
-  metadata.gz: 93d07716f90c2303a08c144fd006f3d45428b87c413f29c2deb2994d2369511f0bb65e8239323b1690c55869d22c001129de45b703d5fd2be1d8cd2afd07e22c
-  data.tar.gz: 47a6a25cecfe0323789857490d2d80f40be055cf67a2bffb5e3057bc0e29d9ad619dce6fcf66002ad110a176a3b23d805c435804c678f47d42ef08e2c91aaeed
+  metadata.gz: 41c2815e44c5bec45bb9b907690d601a025d06c8285c68f0a87ae0d7309db2b8a7fd88149713cd2d4ca34c8dd88afda2c9d9ef8c5f564328b38ffaab4f6b5852
+  data.tar.gz: a5bf34fa9de6034abd1532ebefc0fcd75138cc624c1af6206f0c87f15571009670bccf31d85f59b29d715c3bac7f17e02584aa5c895893d9b88d8080c9fb633c

data/CHANGELOG.md

@@ -10,14 +10,34 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Fixed
 ### Removed
 
+## [1.1.2] 2023-03-17
+### Added
+* GitLab CI config
+### Changed
+* Upgraded to RuboCop v1.48.1
+    * Compatible with rubocop-packaging ~> 0.5.2
+* Improved development documentation
+* Improved documentation on SemVer adherence
+### Fixed
+* Stop defining global variable in version.rb
+
+## [1.1.1] 2022-12-20
+### Fixed
+* Do not require version.rb from gemspec so code coverage is accurate from both `rake` and `rspec`
+* Typos in CHANGELOG & Documentation
+### Changed
+* Minimum Code Coverage == 100%
+
 ## [1.1.0] 2022-12-18
 ### Changed
 * Update to rubocop `~> 1.40.0`
-* ### Added
+### Added
 * Gem release ships with `SHA512` and `SHA256` checksums
 * Release is securely signed by author
 * Document release process in `CONTRIBUTING.md`
-* Improved Documentation related to Three Guarantees
+* Documentation of Three Guarantees:
+    * `rubocop-ruby2_7` (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.
 
 ## [1.0.6] 2022-06-08
 ### Changed
@@ -51,7 +71,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Added
 * Initial release
 
-[Unreleased]: https://github.com/rubocop-lts/rubocop-ruby3_0/compare/v1.1.0...HEAD
+[Unreleased]: https://github.com/rubocop-lts/rubocop-ruby3_0/compare/v1.1.2...HEAD
+[1.1.2]: https://github.com/rubocop-lts/rubocop-ruby3_0/compare/v1.1.1...v1.1.2
+[1.1.1]: https://github.com/rubocop-lts/rubocop-ruby3_0/compare/v1.1.0...v1.1.1
 [1.1.0]: https://github.com/rubocop-lts/rubocop-ruby3_0/compare/v1.0.6...v1.1.0
 [1.0.6]: https://github.com/rubocop-lts/rubocop-ruby3_0/compare/v1.0.5...v1.0.6
 [1.0.5]: https://github.com/rubocop-lts/rubocop-ruby3_0/compare/v1.0.4...v1.0.5

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.
@@ -25,13 +26,12 @@ See: [RubyGems Security Guide][rubygems-security-guide]
 
 ## Contributors
 
-[![Contributors][🖐contributors-img]][🖐contributors]
+See: [https://gitlab.com/rubocop-lts/rubocop-ruby3_)/-/graphs/main][🖐contributors]
 
 [comment]: <> (Following links are used by README, CONTRIBUTING, Homepage)
 
 [conduct]: https://gitlab.com/rubocop-lts/rubocop-ruby3_0/-/blob/main/CODE_OF_CONDUCT.md
 [🖐contributors]: https://gitlab.com/rubocop-lts/rubocop-ruby3_0/-/graphs/main
-[🖐contributors-img]: https://img.shields.io/github/contributors-anon/rubocop-lts/rubocop-ruby3_0
 [🚎src-main]: https://gitlab.com/rubocop-lts/rubocop-ruby3_0/-/tree/main
 [🏘chat]: https://gitter.im/rubocop-lts/community
 [rubygems-security-guide]: https://guides.rubygems.org/security/#building-gems

data/LICENSE.txt

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2022 Peter Boling
+Copyright (c) 2022 - 2023 Peter Boling
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

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
-**install** on (1), **run** on (2), and **analyze code** (3) intended to support any version of Ruby >= 3.0.
+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
 
@@ -203,9 +220,12 @@ 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).
+To install this gem onto your local machine, run `bundle exec rake install`.
 
 ## ⚡️ Contributing
 
@@ -244,7 +264,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
 

data/lib/rubocop/ruby3_0/version.rb

@@ -2,6 +2,6 @@
 
 module Rubocop
   module Ruby30
-    VERSION = "1.1.0"
+    VERSION = "1.1.2"
   end
 end

data/rubocop.yml

@@ -1,3 +1,10 @@
 AllCops:
   TargetRubyVersion: 3.0
   NewCops: enable
+
+Gemspec/DevelopmentDependencies:
+  EnforcedStyle: Gemfile
+  AllowedGems:
+    - rake
+    - rspec
+    - yard

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rubocop-ruby3_0
 version: !ruby/object:Gem::Version
-  version: 1.1.0
+  version: 1.1.2
 platform: ruby
 authors:
 - Peter Boling
@@ -36,7 +36,7 @@ cert_chain:
   gwGrEXGQGDZ0NIgBcmvMOqlXjkGQwQvugKycJ024z89+fz2332vdZIKTrSxJrXGk
   4/bR9A==
   -----END CERTIFICATE-----
-date: 2022-12-18 00:00:00.000000000 Z
+date: 2023-03-17 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.48.1
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.40.0
+        version: 1.48.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-ruby3_0
-  source_code_uri: https://github.com/rubocop-lts/rubocop-ruby3_0/tree/v1.1.0
-  changelog_uri: https://github.com/rubocop-lts/rubocop-ruby3_0/blob/v1.1.0/CHANGELOG.md
+  source_code_uri: https://github.com/rubocop-lts/rubocop-ruby3_0/tree/v1.1.2
+  changelog_uri: https://github.com/rubocop-lts/rubocop-ruby3_0/blob/v1.1.2/CHANGELOG.md
   bug_tracker_uri: https://github.com/rubocop-lts/rubocop-ruby3_0/issues
-  documentation_uri: https://www.rubydoc.info/gems/rubocop-ruby3_0/1.1.0
+  documentation_uri: https://www.rubydoc.info/gems/rubocop-ruby3_0/1.1.2
   funding_uri: https://liberapay.com/pboling
   wiki_uri: https://github.com/rubocop-lts/rubocop-ruby3_0/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.2.33
+rubygems_version: 3.4.8
 signing_key:
 specification_version: 4
 summary: Semantically Versioned RuboCop Dependency