From b80ea403c23f47e53d6e638e016aa19022786989 Mon Sep 17 00:00:00 2001 From: Jeff Widman Date: Mon, 1 Aug 2022 11:22:20 -0700 Subject: [PATCH] Clarify the API stability wording Previously the wording implied that between major versions the API won't change. But it's pretty clear from the surrounding wording and general semvar concept that the API _will_ change between major versions... it's only between minor/patch versions that it won't change. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 689fa4a7fa7..b5e4be2ef52 100644 --- a/README.md +++ b/README.md @@ -46,7 +46,7 @@ If you'd rather install RuboCop using `bundler`, add a line for it in your `Gemf gem 'rubocop', require: false ``` -RuboCop is stable between major versions, both in terms of API and cop configuration. +RuboCop is stable between minor versions, both in terms of API and cop configuration. We aim to ease the maintenance of RuboCop extensions and the upgrades between RuboCop releases. All big changes are reserved for major releases. To prevent an unwanted RuboCop update you might want to use a conservative version lock