π¦Ύ Rubocop::Lts
if ci_badges.map(&:color).detect { it != "green"} βοΈ let me know on Discord or RubyForum, as I may have missed the notification.
if ci_badges.map(&:color).all? { it == "green"} ποΈ send money so I can do more of this. FLOSS maintenance is now my full-time job.
π£ How will this project approach the September 2025 hostile takeover of RubyGems? ποΈ
I've summarized my thoughts in this blog post.
π» Synopsis 
The complete documentation site is at https://rubocop-lts.gitlab.io/
Although the situation has improved somewhat, it remains unsafe to upgrade RuboCop, or Standard, in a project that supports EOL Rubies.
I hope it helps others avoid some of the challenges I've had with library maintenance, and supporting decade-old mission-critical applications.
Avoid bike-shedding, use rubocop-lts in every project, and
let it manage your linting complexity!
If the rubocop-lts stack of libraries has helped you, or your organization,
please support my efforts by making a donation, or becoming a sponsor.
Quick Links
- π± Convention > Configuration
- π± Releases
- π± How to Upgrade Ruby (1.8 to 3.2)!
- π©βπ» Org Health
- β¨ Installation
- π§ Usage
- β‘οΈ Contributing
- π Contributors
- π License
- Β© Copyright
- π€ Code of Conduct
- π Versioning
This README
This README has two jobs:
- Describe the branch you are reading right now.
- Index the
rubocop-ltsbranch stack so you can jump to the release line matching the oldest Ruby you still support.
- π³ This Branch
- π§ Branch Stack
- π©βπ» Project Health
- β¨ Installation
- π§ Usage
This Branch π³
This README is for the rubocop-lts 24.x line enforcing Ruby 3.2 style.
Use this branch when you want RuboCop to enforce syntax and style compatible with Ruby 3.2. For a different linting target, choose the matching branch and major version line from the table below.
This gem configures many gems for you:
- rubocop
- rubocop-gradual
- rubocop-md
- rubocop-rake
- rubocop-thread_safety
- standard
- standard-performance (incl. rubocop-performance)
- standard-custom
- standard-rubocop-lts (ruby version-specific rules)
- rubocop-lts-ruby (Ruby core and standard library API availability checks)
And optionally, if you are using RSpec:
- rubocop-lts-rspec (which loads
rubocop-rspec,rubocop-rspec-extra,rubocop-env, andrubocop-factory_bot)
And optionally, if you are building a RubyGem:
- rubocop-packaging
And optionally, if you are building a Rails app:
- standard-rails (incl. rubocop-rails)
- betterlint
Branch Stack π§
Each even-numbered rubocop-lts major version is maintained on a branch named
for the Ruby syntax and style it teaches RuboCop to enforce. This is a linting
target, not a promise that the gem's own runtime dependencies execute on that
Ruby.
| Ruby Style Enforced | rubocop-lts line |
Branch |
|---|---|---|
| Ruby 1.8 | 0.x | r1_8-even-v0 |
| Ruby 1.9 | 2.x | r1_9-even-v2 |
| Ruby 2.0 | 4.x | r2_0-even-v4 |
| Ruby 2.1 | 6.x | r2_1-even-v6 |
| Ruby 2.2 | 8.x | r2_2-even-v8 |
| Ruby 2.3 | 10.x | r2_3-even-v10 |
| Ruby 2.4 | 12.x | r2_4-even-v12 |
| Ruby 2.5 | 14.x | r2_5-even-v14 |
| Ruby 2.6 | 16.x | r2_6-even-v16 |
| Ruby 2.7 | 18.x | r2_7-even-v18 |
| Ruby 3.0 | 20.x | r3_0-even-v20 |
| Ruby 3.1 | 22.x | r3_1-even-v22 |
| Ruby 3.2 | 24.x | r3_2-even-v24 |
main is intentionally part of templating work so it can seed the next stacked
branch, but release and install workflows should use the released branch line
that matches your Ruby floor.
Project Health π©βπ»
π‘ Info you can shake a stick at
| Tokens to Remember |   |
|---|---|
| Works with JRuby |    |
| Works with Truffle Ruby |      |
| Works with MRI Ruby 4 |   |
| Works with MRI Ruby 3 |    |
| Support & Community |      |
| Source |     |
| Documentation |      |
| Compliance |      |
| Style |     |
| Maintainer ποΈ |      |
... π |
    π§ π π π§ͺ |
Compatibility
Compatible with MRI Ruby 3.2+, JRuby, and TruffleRuby.
CI workflows and Appraisals are generated for MRI Ruby 3.2+.
This test floor is configured by ruby.test_minimum in .kettle-jem.yml and
may be higher than the gem's runtime compatibility floor when legacy Rubies are
not practical for the current toolchain.
The amazing test matrix is powered by the kettle-dev stack.
How kettle-dev manages complexity in tests
| Gem | Source | Role | Total downloads |
|---|---|---|---|
| appraisal2 | GitHub | multi-dependency Appraisal matrix generation |  |
| appraisal2-rubocop | GitHub | RuboCop Appraisal generator integration |  |
| kettle-dev | GitHub | development, release, and CI workflow tooling |  |
| kettle-jem | GitHub | Appraisals & CI workflow templates |  |
| kettle-soup-cover | GitHub | SimpleCov coverage policy and reporting |  |
| kettle-test | GitHub | standard test runner and coverage harness |  |
| turbo_tests2 | GitHub | parallel test execution |  |
Federated DVCS
Find this repo on federated forges (Coming soon!)
| Federated DVCS Repository | Status | Issues | PRs | Wiki | CI |
|---|---|---|---|---|---|
| π§ͺ rubocop-lts/rubocop-lts on GitLab | The Truth | π | π | π | π Tiny Matrix |
| π§ rubocop-lts/rubocop-lts on CodeBerg | An Ethical Mirror (Donate) | π | π | β | βοΈ No Matrix |
| π rubocop-lts/rubocop-lts on GitHub | Another Mirror | π | π | π | π― Full Matrix |
Enterprise Support
Available as part of the Tidelift Subscription.
Need enterprise-level guarantees?
The maintainers of this and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source packages you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact packages you use.
- π‘Subscribe for support guarantees covering all your FLOSS dependencies
- π‘Tidelift is part of Sonar
- π‘Tidelift pays maintainers to maintain the software you depend on!
π@Pointy Haired Boss: An enterprise support subscription is "never gonna let you down", and supports open source maintainers
Alternatively:
β¨ Installation
Install the gem and add to the application's Gemfile by executing:
bundle add rubocop-lts
If bundler is not being used to manage dependencies, install the gem by executing:
gem install rubocop-lts
βοΈ Configuration
Please see the primary configuration and usage documentation.
- π§ Primary Configuration and Usage Documentation.
π§ Basic Usage
Please see the primary configuration and usage documentation.
- π§ Primary Configuration and Usage Documentation.
π¦· FLOSS Funding
While rubocop-lts tools are free software and will always be, the project would benefit immensely from some funding. Raising a monthly budget of... "dollars" would make the project more sustainable.
We welcome both individual and corporate sponsors! We also offer a wide array of funding channels to account for your preferences. Currently, Open Collective is our preferred funding platform.
If you're working in a company that's making significant use of rubocop-lts tools we'd appreciate it if you suggest to your company to become a rubocop-lts sponsor.
You can support the development of rubocop-lts tools via GitHub Sponsors, Liberapay, PayPal, Open Collective and Tidelift.
| π NOTE |
|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| If doing a sponsorship in the form of donation is problematic for your company
from an accounting standpoint, we'd recommend the use of Tidelift,
where you can get a support-like subscription instead. |
Open Collective for Individuals
Support us with a monthly donation and help us continue our activities. [Become a backer]
NOTE: kettle-readme-backers updates this list every day, automatically.
No backers yet. Be the first!
Open Collective for Organizations
Become a sponsor and get your logo on our README on GitHub with a link to your site. [Become a sponsor]
NOTE: kettle-readme-backers updates this list every day, automatically.
No sponsors yet. Be the first!
Another way to support open-source
Iβm driven by a passion to foster a thriving open-source community β a space where people can tackle complex problems, no matter how small. Revitalizing libraries that have fallen into disrepair, and building new libraries focused on solving real-world challenges, are my passions. I was recently affected by layoffs, and the tech jobs market is unwelcoming. Iβm reaching out here because your support would significantly aid my efforts to provide for my family, and my farm (11 π chickens, 2 πΆ dogs, 3 π° rabbits, 8 πβ cats).
If you work at a company that uses my work, please encourage them to support me as a corporate sponsor. My work on gems you use might show up in bundle fund.
Iβm developing a new library, floss_funding, designed to empower open-source developers like myself to get paid for the work we do, in a sustainable way. Please give it a look.
Floss-Funding.dev: ποΈ No network calls. ποΈ No tracking. ποΈ No oversight. ποΈ Minimal crypto hashing. π‘ Easily disabled nags
π Security
See SECURITY.md.
π€ Contributing
If you need some ideas of where to help, you could work on adding more code coverage, check issues or PRs, or use the gem and think about how it could be better.
We so if you make changes, remember to update it.
See CONTRIBUTING.md for more detailed instructions.
π Release Instructions
See CONTRIBUTING.md.
Code Coverage
Coverage service badges
πͺ Code of Conduct
Everyone interacting with this project's codebases, issue trackers,
chat rooms and mailing lists agrees to follow the .
π Contributors
Made with contributors-img.
Also see GitLab Contributors: https://gitlab.com/rubocop-lts/rubocop-lts/-/graphs/main
π Versioning
This library follows for its public API where practical.
For most applications, prefer the Pessimistic Version Constraint with two digits of precision.
For example:
spec.add_dependency("rubocop-lts", "~> 24.0")
π Is "Platform Support" part of the public API? More details inside.
Dropping support for a platform can be a breaking change for affected users. If a release changes supported platforms, it should be called out clearly in the changelog and versioned with that impact in mind.
To get a better understanding of how SemVer is intended to work over a project's lifetime, read this article from the creator of SemVer:
See CHANGELOG.md for a list of releases.
π License
The gem is available as open source under the terms of
the MIT .
Β© Copyright
See LICENSE.md for the official copyright notice.
Copyright holders
- Copyright (c) 2022-2023, 2026 Peter H. Boling
π€ A request for help
Maintainers have teeth and need to pay their dentists. After getting laid off in an RIF in March, and encountering difficulty finding a new one, I began spending most of my time building open source tools. I'm hoping to be able to pay for my kids' health insurance this month, so if you value the work I am doing, I need your support. Please consider sponsoring me or the project.
To join the community or get help, use the RubyForum or Discord.
To say "thanks!" βοΈ Join the community or ποΈ send money.
π 
Please give the project a star β β₯.
Many parts of this project are actively managed by a kettle-jem smart template utilizing StructuredMerge.org merge contracts.
Thanks for RTFM. βΊοΈ
| Field | Value |
|---|---|
| Package | rubocop-lts |
| Description | π¦Ύ Configure RuboCop + a bevy of friends to gradually lint Ruby code |
| Homepage | https://github.com/rubocop-lts/rubocop-lts |
| Source | https://github.com/rubocop-lts/rubocop-lts |
| License | MIT |
| Funding | https://github.com/sponsors/pboling, https://ko-fi.com/pboling, https://liberapay.com/pboling/donate, https://opencollective.com/rubocop-lts, https://thanks.dev/u/gh/pboling, https://tidelift.com/funding/github/rubygems/rubocop-lts, https://www.buymeacoffee.com/pboling |