blog: mention new features in first migration step (#84)

biomejs · Aug 30, 2023 · dd9330f · dd9330f
1 parent 0cf37f7
commit dd9330f
Showing 1 changed file with 1 addition and 5 deletions.
diff --git a/website/src/pages/blog/annoucing-biome.mdx b/website/src/pages/blog/annoucing-biome.mdx
@@ -103,7 +103,7 @@ The team wanted to create a second "Rome", a second version of it. So we fused t
 
 The `rome` package **_won't be maintained anymore_** by the core team, so you won't get any more releases.
 
-1. You should use the `@biomejs/biome` package.
+1. You should use the `@biomejs/biome` package. Note that Biome also comes with a lot of new features and fixes. We've just prepared a [blog post](/blog/biome-v1) for that.
    ```diff
    {
    -  "rome": "12.1.3"
@@ -152,10 +152,6 @@ Biome **still accepts the `rome.json` file** as a configuration, so you don't ne
 
 We will eventually sunset the `rome.json` configuration file for `biome.json`, but Biome will do that for you in the subsequent releases. So, don't worry about updating everything unless you want to.
 
-### A release with a ton of stuff
-
-Biome also comes with a lot of new features and fixes. We've just prepared a [blog post](/blog/biome-v1) for that.
-
 ## The core team
 
 - [Emanuele Stoppa](https://github.com/ematipico): me, the lead of the project 🤓