Skip to content

chore: document minor upgrade with latest versions #19600

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 26, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 11 additions & 13 deletions setup/upgrade_minor.rst
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
Upgrading a Minor Version (e.g. 5.0.0 to 5.1.0)
Upgrading a Minor Version (e.g. 6.3.0 to 6.4.0)
===============================================

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

.. code-block:: diff

{
"...": "...",

"require": {
- "symfony/cache": "5.3.*",
+ "symfony/cache": "5.4.*",
- "symfony/config": "5.3.*",
+ "symfony/config": "5.4.*",
- "symfony/console": "5.3.*",
+ "symfony/console": "5.4.*",
- "symfony/config": "6.3.*",
+ "symfony/config": "6.4.*",
- "symfony/console": "6.3.*",
+ "symfony/console": "6.4.*",
"...": "...",

"...": "A few libraries starting with
symfony/ follow their own versioning scheme. You
do not need to update these versions: you can
upgrade them independently whenever you want",
"symfony/monolog-bundle": "^3.5",
"symfony/monolog-bundle": "^3.10",
},
"...": "...",
}
Expand All @@ -54,8 +52,8 @@ Your ``composer.json`` file should also have an ``extra`` block that you will
"extra": {
"symfony": {
"...": "...",
- "require": "5.3.*"
+ "require": "5.4.*"
- "require": "6.3.*"
+ "require": "6.4.*"
}
}

Expand All @@ -79,7 +77,7 @@ to your code to get everything working. Additionally, some features you're
using might still work, but might now be deprecated. While that's fine,
if you know about these deprecations, you can start to fix them over time.

Every version of Symfony comes with an UPGRADE file (e.g. `UPGRADE-5.4.md`_)
Every version of Symfony comes with an UPGRADE file (e.g. `UPGRADE-6.4.md`_)
included in the Symfony directory that describes these changes. If you follow
the instructions in the document and update your code accordingly, it should be
safe to update in the future.
Expand All @@ -97,5 +95,5 @@ These documents can also be found in the `Symfony Repository`_.
.. include:: /setup/_update_recipes.rst.inc

.. _`Symfony Repository`: https://github.com/symfony/symfony
.. _`UPGRADE-5.4.md`: https://github.com/symfony/symfony/blob/5.4/UPGRADE-5.4.md
.. _`UPGRADE-6.4.md`: https://github.com/symfony/symfony/blob/6.4/UPGRADE-6.4.md
.. _`Rector`: https://github.com/rectorphp/rector