Skip to content

Commit 6bab68e

Browse files
Update upgrade_major.rst
Change 4.0 to 4.1
1 parent 0401973 commit 6bab68e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

setup/upgrade_major.rst

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
.. index::
22
single: Upgrading; Major Version
33

4-
Upgrading a Major Version (e.g. 3.4.0 to 4.0.0)
4+
Upgrading a Major Version (e.g. 3.4.0 to 4.1.0)
55
===============================================
66

77
Every two years, Symfony releases a new major version release (the first number
@@ -30,7 +30,7 @@ backwards incompatible changes. To accomplish this, the "old" (e.g. functions,
3030
classes, etc) code still works, but is marked as *deprecated*, indicating that
3131
it will be removed/changed in the future and that you should stop using it.
3232

33-
When the major version is released (e.g. 4.0.0), all deprecated features and
33+
When the major version is released (e.g. 4.1.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.
3636
3.4.*), you should be able to upgrade without a problem.
@@ -128,7 +128,7 @@ Composer by modifying your ``composer.json`` file:
128128
"...": "...",
129129
130130
"require": {
131-
"symfony/symfony": "^4.0",
131+
"symfony/symfony": "^4.1",
132132
},
133133
"...": "..."
134134
}

0 commit comments

Comments
 (0)