Skip to content

Commit 3a1d28d

Browse files
committed
* unstable_versions.rst - upgrade
1 parent 7de7194 commit 3a1d28d

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

setup/unstable_versions.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Creating a New Project Based on an Unstable Symfony Version
88
-----------------------------------------------------------
99

1010

11-
Suppose that the Symfony 4.0 version hasn't been released yet and you want to create
11+
Suppose that the Symfony 5.4 version hasn't been released yet and you want to create
1212
a new project to test its features. First, `install the Composer package manager`_.
1313
Then, open a command console, enter your project's directory and
1414
run the following command:
@@ -24,7 +24,7 @@ in the ``my_project/`` directory.
2424
Upgrading your Project to an Unstable Symfony Version
2525
-----------------------------------------------------
2626

27-
Suppose again that Symfony 4.0 hasn't been released yet and you want to upgrade
27+
Suppose again that Symfony 5.4 hasn't been released yet and you want to upgrade
2828
an existing application to test that your project works with it.
2929

3030
First, open the ``composer.json`` file located in the root directory of your
@@ -35,16 +35,16 @@ new version and change your ``minimum-stability`` to ``beta``:
3535
3636
{
3737
"require": {
38-
+ "symfony/framework-bundle": "^4.0",
39-
+ "symfony/finder": "^4.0",
38+
+ "symfony/framework-bundle": "^5.4",
39+
+ "symfony/finder": "^5.4",
4040
"...": "..."
4141
},
4242
+ "minimum-stability": "beta"
4343
}
4444
4545
You can also use set ``minimum-stability`` to ``dev``, or omit this line
4646
entirely, and opt into your stability on each package by using constraints
47-
like ``4.0.*@beta``.
47+
like ``5.4.*@beta``.
4848

4949
Finally, from a terminal, update your project's dependencies:
5050

0 commit comments

Comments
 (0)