@@ -7,8 +7,7 @@ they are released as stable versions.
77Creating a New Project Based on an Unstable Symfony Version
88-----------------------------------------------------------
99
10-
11- Suppose that the Symfony 5.4 version hasn't been released yet and you want to create
10+ Suppose that the Symfony 6.0 version hasn't been released yet and you want to create
1211a new project to test its features. First, `install the Composer package manager `_.
1312Then, open a command console, enter your project's directory and
1413run the following command:
@@ -24,7 +23,7 @@ in the ``my_project/`` directory.
2423Upgrading your Project to an Unstable Symfony Version
2524-----------------------------------------------------
2625
27- Suppose again that Symfony 5.4 hasn't been released yet and you want to upgrade
26+ Suppose again that Symfony 6.0 hasn't been released yet and you want to upgrade
2827an existing application to test that your project works with it.
2928
3029First, open the ``composer.json `` file located in the root directory of your
@@ -35,16 +34,16 @@ new version and change your ``minimum-stability`` to ``beta``:
3534
3635 {
3736 "require": {
38- + "symfony/framework-bundle": "^5.4 ",
39- + "symfony/finder": "^5.4 ",
37+ + "symfony/framework-bundle": "^6.0 ",
38+ + "symfony/finder": "^6.0 ",
4039 "...": "..."
4140 },
4241 + "minimum-stability": "beta"
4342 }
4443
4544 You can also use set ``minimum-stability `` to ``dev ``, or omit this line
4645entirely, and opt into your stability on each package by using constraints
47- like ``5.4 .*@beta ``.
46+ like ``6.0 .*@beta ``.
4847
4948Finally, from a terminal, update your project's dependencies:
5049
0 commit comments