release: v1.8.0 (#3033)

CHANGELOG.md

@@ -9,7 +9,7 @@ New entries must be placed in a section entitled `Unreleased`.
 Read
 our [guidelines for writing a good changelog entry](https://github.com/biomejs/biome/blob/main/CONTRIBUTING.md#changelog).
 
-## Unreleased
+## 1.8.0 (2024-06-04)
 
 ### Analyzer
 
@@ -28,6 +28,12 @@ our [guidelines for writing a good changelog entry](https://github.com/biomejs/b
 
 #### New features
 
+- New `clean` command. Use this new command to clean after the `biome-logs` directory, and remove all the log files.
+
+  ```shell
+  biome clean
+  ```
+
 - Add two new options `--only` and `--skip` to the command `biome lint` ([#58](https://github.com/biomejs/biome/issues/58)).
 
   The `--only` option allows you to run a given rule or rule group,
@@ -259,13 +265,19 @@ our [guidelines for writing a good changelog entry](https://github.com/biomejs/b
 
 - Fix a bug where if the formatter was disabled at the language level, it could be erroneously enabled by an
   override that did not specify the formatter section [#2924](https://github.com/biomejs/biome/issues/2924). Contributed by @dyc3
+- Fix [#2990](https://github.com/biomejs/biome/issues/2990), now Biome doesn't add a trailing comma when formatting `biome.json`. Contributed by @dyc3
 
 ### Editors
 
 #### New features
 
 - Add support for LSP Workspaces
 
+#### Enhancements
+
+- The LSP doesn't crash anymore when the configuration file contains errors. If the configuration contains errors, Biome now shows a pop-up to the user, and it will only parse files using the default configuration.
+  Formatting and linting is disabled until the configuration file is fixed. Contributed by @ematipico
+
 #### Bug fixes
 
 - Fixes [#2781](https://github.com/biomejs/biome/issues/2781), by correctly computing the configuration to apply to a specific file. Contributed by @ematipico
@@ -283,6 +295,16 @@ our [guidelines for writing a good changelog entry](https://github.com/biomejs/b
 
 ### Linter
 
+#### Promoted rules
+
+New rules are incubated in the nursery group. Once stable, we promote them to a stable group. The following rules are promoted:
+
+- [useImportRestrictions](https://biomejs.dev/linter/rules/use-import-restrictions/)
+- [noNodejsModules](https://biomejs.dev/linter/rules/no-nodejs-modules/)
+- [useArrayLiterals](https://biomejs.dev/linter/rules/use-array-literals/)
+- [noConstantMathMinMaxClamp](https://biomejs.dev/linter/rules/no-constant-math-min-max-clamp/)
+- [noFlatMapIdentity](https://biomejs.dev/linter/rules/no-flat-map-identity/)
+
 #### New features
 
 - Add [nursery/useDateNow](https://biomejs.dev/linter/rules/use-date-now/). Contributed by @minht11

CONTRIBUTING.md

@@ -390,7 +390,6 @@ When releasing a new version of a Biome, follow these steps:
 1. [ ] Linter rules have a `version` metadata directly defined in their implementation.
    This field is set to `next` for newly created rules.
    This field must be updated to the new version.
-   Then execute `just gen-lint`.
 
 1. [ ] Update the website with the new version number:
    `BIOME_VERSION=<version> just gen-web`.

crates/biome_cli/tests/snapshots/main_configuration/incorrect_rule_name.snap

@@ -52,15 +52,18 @@ biome.json:6:13 deserialize ━━━━━━━━━━━━━━━━━
   - noChildrenProp
   - noConstAssign
   - noConstantCondition
+  - noConstantMathMinMaxClamp
   - noConstructorReturn
   - noEmptyCharacterClassInRegex
   - noEmptyPattern
+  - noFlatMapIdentity
   - noGlobalObjectCalls
   - noInnerDeclarations
   - noInvalidConstructorSuper
   - noInvalidNewBuiltin
   - noInvalidUseBeforeDeclaration
   - noNewSymbol
+  - noNodejsModules
   - noNonoctalDecimalEscape
   - noPrecisionLoss
   - noRenderReturnValue
@@ -80,6 +83,7 @@ biome.json:6:13 deserialize ━━━━━━━━━━━━━━━━━
   - noUnusedVariables
   - noVoidElementsWithChildren
   - noVoidTypeReturn
+  - useArrayLiterals
   - useExhaustiveDependencies
   - useHookAtTopLevel
   - useIsNan