rubocop-lts 22.3.3 → 24.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1d7bf8e6b48610f0fb324c3fbbb5c150e55d9d92801e3f4a36e58af77492021d
-  data.tar.gz: a376315b571122621e3fcc1a7e71686e7440dcf19b32f673b42587a06e061f07
+  metadata.gz: 7306b0d0e9a6931c1f05a547e01b5fcd2eb9cf6390696683134b27a8334624bb
+  data.tar.gz: a650e8392bd71cae446a707ac9f3ca95a34681763461a8c53e9c9e09c0ed73a3
 SHA512:
-  metadata.gz: 691be17e5274f1767b9bc5653c6a5e53eafd1bfaad7f1a0d0cb6ff09ad304c6d18e1abb190612b55e1c560224c722587ea5c0771fb02b7e2a295ea39cc768719
-  data.tar.gz: 2ded20aaf7e9796dffb7a67c1756105ff87adae14d75f9cf18ac4e68d3b09e039a72434e90de611f06751cb9190a930a03f881e0460e3c8673ae87431ee4bb98
+  metadata.gz: 9c66ee60d2491163443a349e3526aca48dc542fad7451c37cdb9a0ad65bf96bd4715847fc220d344107ed37064a66e62358b15b8990255c5af2a713d2e0e709c
+  data.tar.gz: f6f4fffcbc0cd990de1f5cc7c31cfeb4e4dee2f68f2d667d269ac47a4bcec7ea362674a5f4fd90d47e423f35b4905158874fb5447858550252bddf91b8a0febd

data/CHANGELOG.md

@@ -1,247 +1,18 @@
 # 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][📗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
+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).
 
 ## [Unreleased]
-
-### Added
-
-### Changed
-
-### Deprecated
-
-### Removed
-
-### Fixed
-
-### Security
-
-## [22.3.3] - 2026-09-09
-
-- TAG: [v22.3.3][22.3.3t]
-- COVERAGE: 100.00% -- 15/15 lines in 2 files
-- BRANCH COVERAGE: 0.00% -- 0/0 branches in 2 files
-- 42.86% documented
-
-### Added
-
-- kettle-jem-template-20260720-005 - README Support & Community links now
-  include RubyForum.
-- kettle-jem-template-20260726-001 - Projects now include YARD lint
-  configuration and documentation dependencies so documentation issues fail
-  before generated docs are refreshed.
-- kettle-jem-template-20260727-001 - Spec harness documentation now lists the
-  RSpec helpers provided by `kettle-test`.
-
-### Changed
-
-- kettle-jem-template-20260716-002 - Gemspecs now ship fewer repository-only
-  files, reducing package noise for downstream packagers.
-- kettle-jem-template-20260720-002 - Development Gemfiles now use the released
-  `tree_sitter_language_pack` gem 1.13.3 or newer by default.
-- kettle-jem-template-20260725-002 - Version specs now use `anonymous_loader` to
-  cover `version.rb` without redefining constants, or are removed when version
-  specs are not managed for the project.
-- kettle-jem-template-20260728-001 - Generated Ruby workflows now use clearer
-  setup-ruby-flash planning and can prepare appraisal-only jobs without
-  installing the main Gemfile bundle.
-
-- kettle-jem-template-20260801-001 - Generated README gem dashboard links now
-  use ClickGems instead of BestGems.
-
-- [kc] kettle-jem/prepare: updated 28 project files:
-  - configuration (1)
-  - dependencies (27)
-
-- [kc] kettle-jem/template: updated 48 project files:
-  - code and tests (3)
-  - configuration (1)
-  - dependencies (6)
-  - documentation (2)
-  - other (17)
-  - workflows (19)
-
-### Fixed
-
-- kettle-jem-template-20260720-003 - StructuredMerge Git diff driver config now
-  uses the installed `smorg-rb` driver command.
-- kettle-jem-template-20260725-001 - Release pull request branches beginning
-  with `feature/release` now run JRuby and TruffleRuby workflows.
-- kettle-jem-template-20260726-002 - Generated version files now document their
-  version namespace and constants, reducing warning-only YARD lint output.
-- kettle-jem-template-20260726-003 - Coverage upload steps now treat Coveralls,
-  QLTY, and Codecov as optional, so provider outages do not fail CI when local
-  coverage thresholds still pass.
-- kettle-jem-template-20260728-002 - Generated RuboCop configs now ignore the
-  same `gemfiles/vendor/bundle` tree as `.gitignore`, so vendored dependency
-  installs are not reported as project lint debt.
-- kettle-jem-template-20260728-003 - Generated dep-heads workflows now run
-  TruffleRuby jobs with current RubyGems and Bundler, avoiding setup failures
-  before the test suite starts.
-- kettle-jem-template-20260728-004 - Generated dep-heads workflows now use the
-  setup-ruby Bundler install path for direct appraisal Gemfiles, avoiding rv
-  lockfile parser failures on Git and path dependencies.
-- kettle-jem-template-20260728-005 - VersionGem bootstrap now creates the
-  missing canonical version spec when a project only has shim namespace version
-  specs.
-- kettle-jem-template-20260730-001 - Gemspec package file enumeration now runs
-  relative to the gemspec directory, so release package contents stay correct
-  even when the gemspec is loaded from another working directory.
-
-- kettle-jem-template-20260801-002 - Generated RSpec helpers now normalize
-  managed configuration block bindings structurally, preventing mixed block
-  parameter names from producing invalid configuration after a merge.
-- kettle-jem-template-20260801-003 - Generated project metadata and
-  documentation now normalize configured underscore hostnames to valid
-  hyphenated hostnames.
-- kettle-jem-template-20260801-004 - Generated organization README logos now
-  use GitHub's stable organization avatar endpoint instead of assuming a
-  matching Galtzo-hosted asset exists.
-
-- kettle-jem-template-20260802-001 - Devcontainer JSON files now merge as JSONC,
-  preserving comments and trailing commas during template updates.
-
-- Fix README reference definitions and local navigation links so release validation succeeds.
-
-- Run CI on branch-stack release targets.
-
-## [22.3.2] - 2026-07-03
-
-- TAG: [v22.3.2][22.3.2t]
-- COVERAGE: 100.00% -- 15/15 lines in 2 files
-- BRANCH COVERAGE: 0.00% -- 0/0 branches in 2 files
-- 14.29% documented
-
-### Fixed
-
-- Allow release branch-stack pushes to start the managed GitHub Actions workflows.
-
-- Removed stale Shopify wording from gem metadata and retired legacy context Gemfiles.
-- Refreshed the locked dependency set to use released RuboCop-LTS RSpec tooling.
-
-- Package configured license files in gem release file lists.
-
-## [22.3.1] - 2026-06-28
-
-- TAG: [v22.3.1][22.3.1t]
-- COVERAGE: 100.00% -- 15/15 lines in 2 files
-- BRANCH COVERAGE: 0.00% -- 0/0 branches in 2 files
-- 14.29% documented
-
-### Added
-
-- Added support for JRuby 10.1 and TruffleRuby 34.0.
-
-### Fixed
-
-- Restored the destination `spec.files` package declaration so the built gem
-  includes its `config/*.yml` RuboCop configuration files.
-
-## [22.3.0] - 2026-06-01
-
-### Added
-
-### Changed
-
-- Updated dependency floors to the latest RuboCop-LTS family releases.
-- Raised the minimum supported Ruby version to 3.2.
-
-### Fixed
-
-- Added the missing previous release entry to the changelog.
-
-### Removed
-
-- Removed support for running this gem on Ruby < 3.2.
-
-## [22.2.0] - 2026-05-30
-
 ### Added
-
 ### Changed
-
-- Updated the `standard-rubocop-lts` dependency floor to `2.0.0`.
-
 ### Fixed
-
 ### Removed
 
-- Removed remaining `rubocop-shopify` usage from the active development toolchain.
-
-## [22.1.3] - 2023-05-30
-
+## [24.0.0] - 2023-05-22
 ### Added
+- Initial even release supporting Ruby >= 3.2
 
-- `config/base.yml` for all shared configs
-- `Rubocop::Lts.install_tasks` to roll-up rake tasks from dependencies (e.g. rubocop_gradual)
-
-## [22.1.2] - 2023-05-22
-
-### Changed
-
-- Oops, minimum Ruby version is 3.1, for real this time.
-
-## [22.1.1] - 2023-05-22
-
-### Changed
-
-- Minimum Ruby version is 3.1
-
-## [22.1.0] - 2023-05-22
-
-### Changed
-
-- Bumped dependency rubocop-ruby3_1 to ~> 2.0.4
-
-## [22.0.1] - 2022-06-09
-
-### Added
-
-- Improve, and dry up documentation
-
-### Changed
-
-- Bumped dependency rubocop-ruby3_1 to ~> 1.0.6
-
-### Fixed
-
-- Allow install up to Ruby < 4, which allows running against current Ruby HEAD @ 3.2-dev
-
-## [22.0.0] - 2022-05-23
-
-- TAG: [v22.0.0][22.0.0t]
-
-### Added
-
-- Initial even release supporting Ruby >= 3.1
-
-[Unreleased]: https://github.com/rubocop-lts/rubocop-lts/compare/v22.3.3...HEAD
-[22.3.3]: https://github.com/rubocop-lts/rubocop-lts/compare/v22.3.2...v22.3.3
-[22.3.3t]: https://github.com/rubocop-lts/rubocop-lts/releases/tag/v22.3.3
-[22.3.2]: https://github.com/rubocop-lts/rubocop-lts/compare/v22.3.1...v22.3.2
-[22.3.2t]: https://github.com/rubocop-lts/rubocop-lts/releases/tag/v22.3.2
-[22.3.1]: https://github.com/rubocop-lts/rubocop-lts/compare/v22.3.0...v22.3.1
-[22.3.1t]: https://github.com/rubocop-lts/rubocop-lts/releases/tag/v22.3.1
-[22.3.0]: https://gitlab.com/rubocop-lts/rubocop-lts/-/compare/v22.2.0...v22.3.0
-[22.2.0]: https://gitlab.com/rubocop-lts/rubocop-lts/-/compare/v22.1.3...v22.2.0
-[22.1.3]: https://github.com/rubocop-lts/rubocop-lts/compare/v22.1.2...v22.1.3
-[22.1.2]: https://github.com/rubocop-lts/rubocop-lts/compare/v22.1.1...v22.1.2
-[22.1.1]: https://github.com/rubocop-lts/rubocop-lts/compare/v22.1.0...v22.1.1
-[22.1.0]: https://github.com/rubocop-lts/rubocop-lts/compare/v22.0.1...v22.1.0
-[22.0.1]: https://github.com/rubocop-lts/rubocop-lts/compare/v22.0.0...v22.0.1
-[22.0.0]: https://github.com/rubocop-lts/rubocop-lts/releases/tag/v22.0.0
-[22.0.0t]: https://github.com/rubocop-lts/rubocop-lts/releases/tag/v22.0.0
+[Unreleased]: https://github.com/rubocop-lts/rubocop-lts/compare/v24.0.0...HEAD
+[24.0.0]: https://gitlab.com/rubocop-lts/rubocop-lts/-/tags/v24.0.0

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## 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 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:
+
+* 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
+
+Examples of unacceptable behavior include:
+
+* 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
+* 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 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.
+
+## 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.
+
+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:
+
+### 1. Correction
+
+**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.
+
+### 2. Warning
+
+**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.
+
+### 3. Temporary Ban
+
+**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.
+
+### 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.
+
+**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.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+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.

data/CONTRIBUTING.md

@@ -0,0 +1,39 @@
+## Contributing
+
+Bug reports and pull requests are welcome on GitLab at [https://gitlab.com/rubocop-lts/rubocop-lts][🚎src-main]
+. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to
+the [code of conduct][conduct].
+
+To submit a patch, please fork the project and create a patch with tests. Once you're happy with it send a pull request
+and post a message to the [gitter chat][🏘chat].
+
+## Release
+
+To release a new version:
+
+1. Run `bin/setup && bin/rake` as a tests, coverage, & linting sanity check.
+2. update the version number in `version.rb`
+3. Run `bin/setup && bin/rake` again as a secondary check, and to update `Gemfile.lock`.
+4. run `bundle exec rake build:checksum`
+5. move the built gem to project root
+6. run `bin/checksum` to create the missing SHA256 checksum
+7. move the built gem back to `pkg/`
+8. commit the changes
+9. 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.
+See: [RubyGems Security Guide][rubygems-security-guide]
+
+## Contributors
+
+See: [https://gitlab.com/rubocop-lts/rubocop-lts/-/graphs/main][🖐contributors]
+
+[comment]: <> (Following links are used by README, CONTRIBUTING, Homepage)
+
+[🤝conduct]: https://gitlab.com/rubocop-lts/rubocop-lts/-/blob/main/CODE_OF_CONDUCT.md
+[🖐contributors]: https://gitlab.com/rubocop-lts/rubocop-lts/-/graphs/main
+[🚎src-main]: https://gitlab.com/rubocop-lts/rubocop-lts/-/tree/main
+[🏘chat]: https://gitter.im/rubocop-lts/community
+[rubygems-security-guide]: https://guides.rubygems.org/security/#building-gems
+[rubygems]: https://rubygems.org

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2022 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
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.