You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: setup/upgrade_minor.rst
+9-11Lines changed: 9 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -21,25 +21,23 @@ There are two steps to upgrading a minor version:
21
21
1) Update the Symfony Library via Composer
22
22
------------------------------------------
23
23
24
-
Your composer.json file should already be configured to allow your Symfony packages to be upgraded minor versions. But, if a package was not upgraded that should have been, check your ``composer.json`` file.
24
+
Your ``composer.json`` file should already be configured to allow your Symfony
25
+
packages to be upgraded to minor versions. But, if a package was not upgraded,
26
+
check that the version constrains of your Symfony dependencies are like this:
Copy file name to clipboardExpand all lines: setup/upgrade_patch.rst
+5-2Lines changed: 5 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,12 @@ Upgrading a Patch Version (e.g. 4.1.0 to 4.1.1)
6
6
7
7
When a new patch version is released (only the last number changed), it is a
8
8
release that only contains bug fixes. This means that upgrading to a new patch
9
-
version is *really* easy:
9
+
version is *really* easy.
10
10
11
-
To upgrade to a new "patch" release, see the :doc:Upgrading a Minor Version </setup/upgrade_minor> documentation. Thanks to Symfony's backwards compatibility promise, it's always safe to upgrade to the latest "minor" version.
11
+
To upgrade to a new "patch" release, read the
12
+
:doc:`Upgrading a Minor Version </setup/upgrade_minor>` article. Thanks to
0 commit comments