rubocop-ruby3_1 3.0.2 → 3.0.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4cff16513f8bffb0592b13cad1130577afe44189b3fd6e6af5e44a7458215d70
-  data.tar.gz: 05f089146a4d7542c22233b714d1a8a019cd01fbfd27a5cff985c4ec2effb6a0
+  metadata.gz: 7cb47c4b060b873178a9f25a60aeecadcce4e5b409cf1133f493b3c4f529e799
+  data.tar.gz: 5b2a20d23dce7361a340f879436b10d4ca77aff55ba54869c4af54dfdd374854
 SHA512:
-  metadata.gz: 63bdd792ff7d8affa051e3902cf9ae3b5422a63c1029af0c4a07df48bf1cd6801cf71716d05b39a42c48090c86ff9beabbdb4d596170ce8453357506446103f5
-  data.tar.gz: 04e593f03ff7adcddbb9771231cc4c96ed4273abac73064f80d922f494d1c8edfe5dc91b17bb5cc44d844e2e53031f3f9362366e195a7dab964667bb7f79ebb3
+  metadata.gz: 6a6f4afc5544a0286cc1bd79d42ae9f48479c62969c8fa4d4739d11fb238617c9c16825a4ccd4a89f1bd266032ca2a5ab6b3e3e904e93e9ca52b4054e0506ca7
+  data.tar.gz: 376f26ef88440bf6ba81c143244ff5186fa57339c8d7ccc248102852e88dd752af5acd2b160ce8210747f5e8e0edc2a189901de2fb67a0fede6a68dbe9d02a22

data/CHANGELOG.md

@@ -1,18 +1,73 @@
 # Changelog
+
+[![SemVer 2.0.0][📌semver-img]][📌semver] [![Keep-A-Changelog 1.0.0][📗keep-changelog-img]][📗keep-changelog]
+
 All notable changes to this project will be documented in this file.
 
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+The format is based on [Keep a Changelog][📗keep-changelog],
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
+and [yes][📌major-versions-not-sacred], platform and engine support are part of the [public API][📌semver-breaking].
+Please file a bug if you notice a violation of semantic versioning.
+
+[📌semver]: https://semver.org/spec/v2.0.0.html
+[📌semver-img]: https://img.shields.io/badge/semver-2.0.0-FFDD67.svg?style=flat
+[📌semver-breaking]: https://github.com/semver/semver/issues/716#issuecomment-869336139
+[📌major-versions-not-sacred]: https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
+[📗keep-changelog]: https://keepachangelog.com/en/1.0.0/
+[📗keep-changelog-img]: https://img.shields.io/badge/keep--a--changelog-1.0.0-FFDD67.svg?style=flat
 
 ## [Unreleased]
+
 ### Added
+
 ### Changed
-### Fixed
+
+### Deprecated
+
 ### Removed
 
+### Fixed
+
+### Security
+
+## [3.0.5] - 2026-06-28
+
+- TAG: [v3.0.5][3.0.5t]
+- COVERAGE: 55.17% -- 16/29 lines in 5 files
+- BRANCH COVERAGE: 0.00% -- 0/2 branches in 5 files
+- 42.86% documented
+
+### Fixed
+
+- Restored the gemspec `spec.files` declaration so packaged gems include the
+  intended public files and configuration payload.
+
+## [3.0.4] - 2026-06-25
+
+- TAG: [v3.0.4][3.0.4t]
+- COVERAGE: 55.17% -- 16/29 lines in 5 files
+- BRANCH COVERAGE: 0.00% -- 0/2 branches in 5 files
+- 42.86% documented
+
+### Added
+
+- Added support for JRuby 10.1 and TruffleRuby 34.0.
+
+### Changed
+
+- Retemplated project metadata and CI/development automation with `kettle-jem` v7.0.0.
+
+### Fixed
+
+- Restored `docs/CNAME` so the generated documentation site keeps its custom domain.
+- Corrected misspelled contact metadata to use `galtzo.com`.
+
 ## [3.0.2] 2026-06-01
+
 ### Added
+
 ### Changed
+
 - Corrected gem metadata to declare the Ruby 3.2 runtime floor that has been implicit since the last major release.
 - Updated dependency floors:
   - `version_gem` to `~> 1.1`, `>= 1.1.9`.
@@ -23,42 +78,61 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - `standard-rubocop-lts` to `~> 2.0`, `>= 2.0.3`.
   - Release, lint, documentation, and test dependencies to their latest compatible floors.
 - Updated direct dependency floors and moved `rubocop-md` to plugin loading.
+
 ### Fixed
+
 ### Removed
 
 ## [3.0.1] 2026-06-01
+
 ### Added
+
 ### Changed
+
 - Load `rubocop-thread_safety` through RuboCop's plugin API.
+
 ### Fixed
+
 ### Removed
 
 ## [3.0.0] 2026-05-30
+
 ### Added
+
 ### Changed
+
 - Tidelift for Reporting Security vulnerabilities
 - Updated `standard-rubocop-lts` dependency to the `2.x` series.
+
 ### Fixed
+
 ### Removed
+
 - rubocop-shopify because they boiled the ocean
   - turning cops off isn't copacetic with the goal of strict compatibility
 
 ## [2.0.6] 2023-06-13
+
 ### Changed
+
 - Moved development dependencies out of gemspec
 - rubocop to 1.52.1
 - rubocop-shopify to 2.14
 - standard-custom to 1.0.1
 - standard-rubocop-lts to 1.0.7
 - version_gem to 1.1.3
+
 ### Fixed
+
 - rubocop/rails.yml config
   - betterlint integration
   - standard-rails integration
 - bin/pry now pre-loads this library
 
 ## [2.0.5] 2023-06-05
+
 ### Added
+
 - Dependencies
   - yard-junk
   - redcarpet
@@ -68,28 +142,42 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Some rules should ignore specs/tests
   - Style/MethodCallWithArgsParentheses
   - Style/ClassAndModuleChildren
+
 ### Fixed
+
 - `yard` documentation task
+
 ### Changed
+
 - Added Include to inherit_mode: merge
 - Updated dependency on standard-rubocop-lts
 
 ## [2.0.4] 2023-05-22
+
 ### Fixed
+
 - install_tasks and Railtie loading of rake tasks
+
 ### Changed
+
 - tasks.rake => tasks.rb
 
 ## [2.0.3] 2023-05-21
+
 ### Fixed
+
 - Ship rake tasks in gem package
 
 ## [2.0.2] 2023-05-19
+
 ### Fixed
+
 - Fix rake_tasks hook on Railtie
 
 ## [2.0.1] 2023-05-17 [YANKED]
+
 ### Added
+
 - Configs added for:
   - standard-performance
   - standard-custom
@@ -100,7 +188,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - version_gem
 
 ## [2.0.0] 2023-05-09 [YANKED]
+
 ### Changed
+
 - New/Better configs for:
   - rubocop
   - rubocop-gradual
@@ -116,67 +206,102 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - rubocop-packaging
 
 ## [1.1.4] 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.3] 2022-12-18
+
 ### Added
+
 * Linting to fix CI build
 * Improved Rakefile for YARD docs
 * Documentation of why this gem exists
 
 ## [1.1.2] 2022-12-18
+
 ### Added
+
 * Release is securely signed by author
 
 ## [1.1.1] 2022-12-17
+
 ### Changed
+
 * Update to rubocop `~> 1.40.0`
 * Improved CI workflows (still on GitHub)
 
 ## [1.1.0] 2022-12-7
+
 ### Changed
+
 * Update to rubocop `~> 1.39.0`
 * Migration from GitHub to GitLab [ref](https://github.com/actions/toolkit/issues/1214)
+
 ### Added
+
 * Gem release ships with `SHA512` and `SHA256` checksums
 
 ## [1.0.6] 2022-06-08
+
 ### Changed
+
 * Update to rubocop `~> 1.30.1`
 * Removed test_files from gemspec
 * Add binstubs for bundle, rake, rspec, and rubocop
 
 ## [1.0.5] 2022-06-05
+
 ### Changed
+
 * Update to rubocop `~> 1.30.0`
 
 ## [1.0.4] 2022-05-23
+
 ### Changed
+
 * Update to rubocop `~> 1.29.1`
 
 ## [1.0.3] 2022-05-23
+
 ### Added
+
 * Rubocop => RuboCop typo repair
 * Ruby Version Support Matrix
 * Improved documentation
 
 ## [1.0.2] 2022-05-03
+
 ### Fixed
+
 * Added missing rubocop.yml for inherit_gem directive
 
 ## [1.0.1] 2022-05-02
+
 ### Added
+
 * Documentation
 
 ## [1.0.0] 2022-05-01
+
 ### Added
+
 * Initial release
 
-[Unreleased]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1/-/compare/v3.0.2...HEAD
+[Unreleased]: https://github.com/rubocop-lts/rubocop-ruby3_1/compare/v3.0.5...HEAD
+[3.0.5]: https://github.com/rubocop-lts/rubocop-ruby3_1/compare/v3.0.4...v3.0.5
+[3.0.5t]: https://github.com/rubocop-lts/rubocop-ruby3_1/releases/tag/v3.0.5
+[3.0.4]: https://github.com/rubocop-lts/rubocop-ruby3_1/compare/v3.0.2...v3.0.4
+[3.0.4t]: https://github.com/rubocop-lts/rubocop-ruby3_1/releases/tag/v3.0.4
+[3.0.2]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1/-/compare/v3.0.1...v3.0.2
+[3.0.1]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1/-/compare/v3.0.0...v3.0.1
+[3.0.0]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1/-/compare/v2.0.6...v3.0.0
 [2.0.6]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1/-/compare/v2.0.5...v2.0.6
 [2.0.5]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1/-/compare/v2.0.4...v2.0.5
 [2.0.4]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1/-/compare/v2.0.3...v2.0.4
@@ -195,7 +320,4 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 [1.0.3]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1/-/compare/v1.0.2...v1.0.3
 [1.0.2]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1/-/compare/v1.0.1...v1.0.2
 [1.0.1]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1/-/compare/v1.0.0...v1.0.1
-[1.0.0]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1/-/compare/c4cc8fb6374d338e2c328812b4f74c78dfe5cfbd...v1.0.0
-[3.0.1]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1/-/compare/v3.0.0...v3.0.1
-[3.0.0]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1/-/compare/v2.0.6...v3.0.0
-[3.0.2]: https://gitlab.com/rubocop-lts/rubocop-ruby3_1/-/compare/v3.0.1...v3.0.2
+[1.0.0]: https://github.com/rubocop-lts/rubocop-ruby3_1/compare/c4cc8fb6374d338e2c328812b4f74c78dfe5cfbd...v1.0.0

data/CITATION.cff

@@ -0,0 +1,20 @@
+cff-version: 1.2.0
+title: "rubocop-ruby3_1"
+message: >-
+  If you use this work and you want to cite it,
+  then you can use the metadata from this file.
+type: software
+authors:
+  - given-names: "Peter H."
+    family-names: "Boling"
+    email: "floss@galtzo.com"
+    affiliation: "galtzo.com"
+    orcid: 'https://orcid.org/0009-0008-8519-441X'
+identifiers:
+  - type: url
+    value: 'https://github.com/rubocop-lts/rubocop-ruby3_1'
+    description: "rubocop-ruby3_1"
+repository-code: 'https://github.com/rubocop-lts/rubocop-ruby3_1'
+abstract: >-
+  rubocop-ruby3_1
+license: See license file

data/CODE_OF_CONDUCT.md

@@ -2,83 +2,133 @@
 
 ## Our Pledge
 
-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.
+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, caste, color, religion, or sexual
+identity and orientation.
 
-We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
 
 ## Our Standards
 
-Examples of behavior that contributes to a positive environment for our community include:
+Examples of behavior that contributes to a positive environment for our
+community include:
 
 * Demonstrating empathy and kindness toward other people
 * Being respectful of differing opinions, viewpoints, and experiences
 * Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall community
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
 
 Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
 * Trolling, insulting or derogatory comments, and personal or political attacks
 * Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
 * Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Enforcement Responsibilities
 
-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.
+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.
 
-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.
+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.
 
 ## Scope
 
-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.
+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 email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
 
 ## Enforcement
 
-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.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[![Contact Maintainer][🚂maint-contact-img]][🚂maint-contact].
+All complaints will be reviewed and investigated promptly and fairly.
 
-All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
 
 ## Enforcement Guidelines
 
-Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
 
 ### 1. Correction
 
-**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
 
-**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.
+**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.
 
 ### 2. Warning
 
-**Community Impact**: A violation through a single incident or series of actions.
+**Community Impact**: A violation through a single incident or series of
+actions.
 
-**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.
+**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.
 
 ### 3. Temporary Ban
 
-**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
 
-**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.
+**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.
 
 ### 4. Permanent Ban
 
-**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.
+**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.
 
-**Consequence**: A permanent ban from any sort of public interaction within the community.
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
-available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
 
-Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
 
 For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations
+[🚂maint-contact]: http://www.railsbling.com/contact
+[🚂maint-contact-img]: https://img.shields.io/badge/Contact-Maintainer-0093D0.svg?style=flat&logo=rubyonrails&logoColor=red