Skip to content

Commit 789d6b6

Browse files
committed
[Setup] Fix references of previous version
1 parent 4417f13 commit 789d6b6

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

setup/upgrade_major.rst

+4-4
Original file line numberDiff line numberDiff line change
@@ -33,9 +33,9 @@ it will be removed/changed in the future and that you should stop using it.
3333
When the major version is released (e.g. 6.0.0), all deprecated features and
3434
functionality are removed. So, as long as you've updated your code to stop
3535
using these deprecated features in the last version before the major (e.g.
36-
``4.4.*``), you should be able to upgrade without a problem. That means that
36+
``5.4.*``), you should be able to upgrade without a problem. That means that
3737
you should first :doc:`upgrade to the last minor version </setup/upgrade_minor>`
38-
(e.g. 4.4) so that you can see *all* the deprecations.
38+
(e.g. 5.4) so that you can see *all* the deprecations.
3939

4040
To help you find deprecations, notices are triggered whenever you end up
4141
using a deprecated feature. When visiting your application in the
@@ -104,7 +104,7 @@ done!
104104
.. sidebar:: Using the Weak Deprecations Mode
105105

106106
Sometimes, you can't fix all deprecations (e.g. something was deprecated
107-
in 4.4 and you still need to support 4.3). In these cases, you can still
107+
in 5.4 and you still need to support 5.3). In these cases, you can still
108108
use the bridge to fix as many deprecations as possible and then allow
109109
more of them to make your tests pass again. You can do this by using the
110110
``SYMFONY_DEPRECATIONS_HELPER`` env variable:
@@ -167,7 +167,7 @@ this one. For instance, update it to ``6.0.*`` to upgrade to Symfony 6.0:
167167
"extra": {
168168
"symfony": {
169169
"allow-contrib": false,
170-
- "require": "4.4.*"
170+
- "require": "5.4.*"
171171
+ "require": "6.0.*"
172172
}
173173
}

0 commit comments

Comments
 (0)