update changesets

Author: dotansimha

.changeset/chatty-shoes-hunt.md

@@ -2,8 +2,38 @@
 '@graphql-eslint/eslint-plugin': major
 ---
 
-feat: split `recommended` config to two configs `schema-recommended` and `operations-recommended`
+❗ BREAKING CHANGE ❗
 
-`recommended` and `all` configs were divided to 4 configs `schema-recommended`
-, `operations-recommended`, `schema-all` and `operations-all`. This was done in order to
-use `recommended` and `all` configs in `schema-only` projects where it is not possible to provide operations.
+Split `recommended` config to 2 modes: "schema" and "operations". 
+
+> This was done in order to use `recommended` and `all` configs in `schema-only` projects where it is not possible to provide operations.
+
+`recommended` and `all` configs were divided to 4 configs:
+* `schema-recommended` - enables recommended rules for schema (SDL) development.
+* `schema-all` - enables all recommended rules for schema (SDL) development.
+* `operations-recommended` - enables recommended rules for consuming GraphQL (operations) development.
+* `operations-all` - enables all rules for consuming GraphQL (operations) development.
+
+If you are migrating from v2 where `recommended` was introdued, please change the following: 
+
+```yaml
+{
+  "overrides": [
+    {
+      "files": ["*.js"],
+      "processor": "@graphql-eslint/graphql"
+    },
+    {
+      "files": ["*.graphql"],
+-     "extends": "plugin:@graphql-eslint/schema",
++     "extends": "plugin:@graphql-eslint/schema-recommended"
+    }
+  ]
+}
+```
+
+> If you are in a project that develops the GraphQL schema, you'll need `schema` rules. 
+
+> If you are in a project that develops GraphQL operations (query/mutation/subscription), you'll need `operations` rules.
+
+> If you are in a monorepo project, you probably need both sets of rules.

.changeset/polite-pillows-pump.md

@@ -2,4 +2,6 @@
 '@graphql-eslint/eslint-plugin': major
 ---
 
-feat: `description-style` now have default description style `block`
+❗ BREAKING CHANGE ❗
+
+feat: `description-style` now have default description style `block`.

.changeset/tame-geese-lick.md

@@ -2,4 +2,6 @@
 '@graphql-eslint/eslint-plugin': major
 ---
 
-feat: remove `query` option in `no-root-type` as it's impossible to have write-only schema
+❗ BREAKING CHANGE ❗
+
+feat: remove `query` option in `no-root-type` as it's impossible to have write-only schema.

.changeset/thick-dancers-jump.md

@@ -2,14 +2,16 @@
 '@graphql-eslint/eslint-plugin': major
 ---
 
-feat: rename `avoid` prefix in rules to `no`, remove `avoid-operation-name-prefix`
-and `no-operation-name-suffix`
+❗ BREAKING CHANGE ❗
 
-All rules that had a `avoid` prefix now have a `no` prefix. Rules `avoid-operation-name-prefix`
-and `no-operation-name-suffix` were removed because the same things can be validated
-by `naming-convention` rule.
+- rename `avoid` prefix in rules to `no`. 
+- remove `avoid-operation-name-prefix` and `no-operation-name-suffix`
 
-Before
+All rules that had a `avoid` prefix now have a `no` prefix. 
+
+Rules `avoid-operation-name-prefix` and `no-operation-name-suffix` were removed because the same things can be validated by `naming-convention` rule.
+
+### Before
 
 ```json
 {
@@ -23,7 +25,7 @@ Before
 }
 ```
 
-After
+### After
 
 ```json
 {

.changeset/three-shoes-relax.md

@@ -2,6 +2,8 @@
 '@graphql-eslint/eslint-plugin': major
 ---
 
+❗ BREAKING CHANGE ❗
+
 feat: add new options for `naming-convention` rule
 
 Options for `naming-convention` are changed. New option `types` includes the following kinds:
@@ -19,10 +21,9 @@ Added new options:
 - `DirectiveDefinition`
 - `VariableDefinition`
 
-Option `QueryDefinition` was removed in favor of `AST` specific
-selector `FieldDefinition[parent.name.value=Query]`.
+Option `QueryDefinition` was removed in favor of `AST` specific selector `FieldDefinition[parent.name.value=Query]`.
 
-Before
+### Before
 
 ```json
 {
@@ -47,7 +48,7 @@ Before
 }
 ```
 
-After
+### After
 
 ```json
 {

.changeset/twenty-bottles-care.md

@@ -2,6 +2,8 @@
 '@graphql-eslint/eslint-plugin': major
 ---
 
+❗ BREAKING CHANGE ❗
+
 feat: add new options for `require-description` rule
 
 Options for `require-description` are changed. New option `types` includes the following kinds:
@@ -13,7 +15,7 @@ Options for `require-description` are changed. New option `types` includes the f
 - `InputObjectTypeDefinition`
 - `UnionTypeDefinition`
 
-Before
+### Before
 
 ```json
 {
@@ -36,7 +38,7 @@ Before
 }
 ```
 
-After
+### After
 
 ```json
 {

README.md

@@ -195,6 +195,12 @@ See [docs/deprecated-rules.md](docs/deprecated-rules.md).
 |[`operations-all`](packages/plugin/src/configs/operations-all.ts)|enables all rules|
 <!-- prettier-ignore-end -->
 
+> If you are in a project that develops the GraphQL schema, you'll need `schema` rules. 
+
+> If you are in a project that develops GraphQL operations (query/mutation/subscription), you'll need `operations` rules.
+
+> If you are in a monorepo project, you probably need both sets of rules.
+
 ## Config usage
 
 For example, to enable the `schema-recommended` config, enable it in your `.eslintrc` file with the `extends` option: