Skip to content

Commit 48eed12

Browse files
committed
minor #16228 [Setup] Change upgrade-minor.rst to reference Symfony 5 (gnito-org)
This PR was merged into the 5.3 branch. Discussion ---------- [Setup] Change upgrade-minor.rst to reference Symfony 5 <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/releases for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `5.x` for features of unreleased versions). --> Commits ------- a0f9329 Change upgrade-minor.rst to reference Symfony 5
2 parents fd217f3 + a0f9329 commit 48eed12

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

setup/upgrade_minor.rst

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

4-
Upgrading a Minor Version (e.g. 4.0.0 to 4.1.0)
4+
Upgrading a Minor Version (e.g. 5.0.0 to 5.1.0)
55
===============================================
66

77
If you're upgrading a minor version (where the middle number changes), then
@@ -24,20 +24,20 @@ There are two steps to upgrading a minor version:
2424
The ``composer.json`` file is configured to allow Symfony packages to be
2525
upgraded to patch versions. But to upgrade to a new minor version, you will
2626
probably need to update the version constraint next to each library starting
27-
``symfony/``. Suppose you are upgrading from Symfony 4.3 to 4.4:
27+
``symfony/``. Suppose you are upgrading from Symfony 5.3 to 5.4:
2828

2929
.. code-block:: diff
3030
3131
{
3232
"...": "...",
3333
3434
"require": {
35-
- "symfony/cache": "4.3.*",
36-
+ "symfony/cache": "4.4.*",
37-
- "symfony/config": "4.3.*",
38-
+ "symfony/config": "4.4.*",
39-
- "symfony/console": "4.3.*",
40-
+ "symfony/console": "4.4.*",
35+
- "symfony/cache": "5.3.*",
36+
+ "symfony/cache": "5.4.*",
37+
- "symfony/config": "5.3.*",
38+
+ "symfony/config": "5.4.*",
39+
- "symfony/console": "5.3.*",
40+
+ "symfony/console": "5.4.*",
4141
"...": "...",
4242
4343
"...": "A few libraries starting with
@@ -57,8 +57,8 @@ Your ``composer.json`` file should also have an ``extra`` block that you will
5757
"extra": {
5858
"symfony": {
5959
"...": "...",
60-
- "require": "4.3.*"
61-
+ "require": "4.4.*"
60+
- "require": "5.3.*"
61+
+ "require": "5.4.*"
6262
}
6363
}
6464
@@ -82,7 +82,7 @@ to your code to get everything working. Additionally, some features you're
8282
using might still work, but might now be deprecated. While that's fine,
8383
if you know about these deprecations, you can start to fix them over time.
8484

85-
Every version of Symfony comes with an UPGRADE file (e.g. `UPGRADE-4.4.md`_)
85+
Every version of Symfony comes with an UPGRADE file (e.g. `UPGRADE-5.4.md`_)
8686
included in the Symfony directory that describes these changes. If you follow
8787
the instructions in the document and update your code accordingly, it should be
8888
safe to update in the future.
@@ -94,4 +94,4 @@ These documents can also be found in the `Symfony Repository`_.
9494
.. include:: /setup/_update_recipes.rst.inc
9595

9696
.. _`Symfony Repository`: https://github.com/symfony/symfony
97-
.. _`UPGRADE-4.4.md`: https://github.com/symfony/symfony/blob/4.4/UPGRADE-4.4.md
97+
.. _`UPGRADE-5.4.md`: https://github.com/symfony/symfony/blob/5.4/UPGRADE-5.4.md

0 commit comments

Comments
 (0)