Skip to content

Commit

Permalink
Tweaks
Browse files Browse the repository at this point in the history
  • Loading branch information
javiereguiluz committed Jul 24, 2018
1 parent 898fb68 commit cef13f8
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 13 deletions.
20 changes: 9 additions & 11 deletions setup/upgrade_minor.rst
Original file line number Diff line number Diff line change
Expand Up @@ -21,25 +21,23 @@ There are two steps to upgrading a minor version:
1) Update the Symfony Library via Composer
------------------------------------------

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.
Your ``composer.json`` file should already be configured to allow your Symfony
packages to be upgraded to minor versions. But, if a package was not upgraded,
check that the version constrains of your Symfony dependencies are like this:

.. code-block:: json
{
"...": "...",
"require": {
"symfony/asset": "^4.0",
"symfony/cache": "^4.0",
"symfony/config": "^4.0",
"symfony/console": "^4.0",
"symfony/expression-language": "^4.0",
"symfony/form": "^4.0",
"symfony/framework-bundle": "^4.0",
"symfony/process": "^4.0",
"symfony/security-bundle": "^4.0",
"symfony/twig-bundle": "^4.0",
"symfony/validator": "^4.0",
"symfony/web-link": "^4.0",
"symfony/yaml": "^4.0"
"symfony/debug": "^4.0",
"symfony/dependency-injection": "^4.0",
"symfony/dotenv": "^4.0",
"...": "..."
},
"...": "...",
}
Expand Down
7 changes: 5 additions & 2 deletions setup/upgrade_patch.rst
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,12 @@ Upgrading a Patch Version (e.g. 4.1.0 to 4.1.1)

When a new patch version is released (only the last number changed), it is a
release that only contains bug fixes. This means that upgrading to a new patch
version is *really* easy:
version is *really* easy.

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.
To upgrade to a new "patch" release, read the
:doc:`Upgrading a Minor Version </setup/upgrade_minor>` article. Thanks to
Symfony's :doc`backwards compatibility promise </contributing/code/bc>`, it's
always safe to upgrade to the latest "minor" version.

.. tip::

Expand Down

0 comments on commit cef13f8

Please sign in to comment.