chore: replace more 1.0 references

docs/composer.md

@@ -82,7 +82,7 @@ As mentioned above, the entire composer configuration for your Flarum site is co
     // It's a list of packages we want, and the versions for each.
     // We'll discuss this shortly.
     "require": {
-        "flarum/core": "^1.0",
+        "flarum/core": "^2.0",
         "flarum/approval": "*",
         "flarum/bbcode": "*",
         "flarum/emoji": "*",
@@ -120,7 +120,7 @@ To read more about version strings, see the relevant [composer documentation](ht
 
 For Flarum projects, there's several types of entries you'll see in the `require` section of your root install's `flarum/core`:
 
-- You MUST have a `flarum/core` entry. This should have an explicit version string corresponding to the major release you want to install. For Flarum 1.x versions, this would be `^1.0`.
+- You MUST have a `flarum/core` entry. This should have an explicit version string corresponding to the major release you want to install. For Flarum 2.x versions, this would be `^2.0`.
 - You should have an entry for each extension you've installed. Some bundled extensions are included by default (e.g. `flarum/tags`, `flarum/suspend`, etc), [others you'll add via composer commands](extensions.md). Unless you have a reason to do otherwise (e.g. you're testing a beta version of a package), we recommend using an asterisk as the version string for extensions (`*`). This means "install the latest version compatible with my flarum/core".
 - Some extensions / features might require PHP packages that aren't Flarum extensions. For example, you need the guzzle library to use the [Mailgun mail driver](mail.md). In these cases, the instructions for the extension/feature in question should explain which version string to use.
 

docs/extend/extending-extensions.md

@@ -24,8 +24,8 @@ For example, if you were building a new theme for the Flarum Tags extension, you
 {
   // ...
   "require": {
-    "flarum/core": "^0.1.0-beta.15",  // Since all extensions need to require core.
-    "flarum/tags": "^0.1.0-beta.15"  // This tells Flarum to treat tags as a dependency of your extension.
+    "flarum/core": "^2.0",  // Since all extensions need to require core.
+    "flarum/tags": "*"  // This tells Flarum to treat tags as a dependency of your extension.
   },
   // ...
 }

docs/extend/static-code-analysis.md

@@ -19,7 +19,7 @@ $ flarum-cli infra phpstan
 First you need to require the `flarum/phpstan` package in your extension. You can do this by running the following command in the root of our extension:
 
 ```bash
-composer require --dev flarum/phpstan:^1.0
+composer require --dev flarum/phpstan:^2.0
 ```
 
 Next, you need to create a `phpstan.neon` file in the root of your extension. This file contains [the configuration for PHPStan](https://phpstan.org/config-reference). You can copy the following configuration into the file:

docs/extend/testing.md

@@ -21,7 +21,7 @@ $ flarum-cli infra backendTesting
 :::
 
 ```bash
-composer require --dev flarum/testing:^1.0
+composer require --dev flarum/testing:^2.0
 ```
 
 Then, you will need to set up a file structure for tests, and add PHPUnit configuration:

docs/faq.md

@@ -2,7 +2,7 @@
 
 ### Is Flarum Stable?
 
-Yes! After 6 years of development, Flarum **1.0.0** was released, and we are now spear-heading the development of Flarum **2.0**.
+Yes! After 6 years of development, Flarum **1.0.0** was released, and we are now spearheading the development of Flarum **2.0**.
 
 ### What's next after stable?