Skip to content

Different way for updating flex projects #9962

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.

Sign up for GitHub

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

Closed
wants to merge 2 commits into from
Closed

Different way for updating flex projects #9962

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2edcbf6
Different way for updating flex projects
Alumbrados Jun 25, 2018
0c2129b
Suggested changes
Alumbrados Jul 17, 2018
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
Prev Previous commit
Suggested changes
  • Loading branch information
@Alumbrados
Alumbrados committed Jul 17, 2018
commit 0c2129bb33cb838fc1ef1c6c6a7835192f032b4a
2 changes: 1 addition & 1 deletion setup/_update_dep_errors.rst.inc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ other Symfony dependencies too. In that case, try the following command:

.. code-block:: terminal

$ composer update "symfony/*" --with-dependencies
$ composer update "symfony/*" --with-all-dependencies

This updates ``symfony/symfony`` and *all* packages that it depends on, which will
include several other packages. By using tight version constraints in
Expand Down
27 changes: 13 additions & 14 deletions setup/upgrade_minor.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,26 +21,25 @@ There are two steps to upgrading a minor version:
1) Update the Symfony Library via Composer
------------------------------------------

First, you need to update all Symfony packages by modifying your ``composer.json`` file
to use the new version (the list of packages may vary depending on what you've installed):
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.

.. code-block:: json

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

"require": {
"symfony/asset": "^4.1",
"symfony/console": "^4.1",
"symfony/expression-language": "^4.1",
"symfony/form": "^4.1",
"symfony/framework-bundle": "^4.1",
"symfony/process": "^4.1",
"symfony/security-bundle": "^4.1",
"symfony/twig-bundle": "^4.1",
"symfony/validator": "^4.1",
"symfony/web-link": "^4.1",
"symfony/yaml": "^4.1"
"symfony/asset": "^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"
},
"...": "...",
}
Expand All @@ -49,7 +48,7 @@ Next, use Composer to download new versions of the libraries:

.. code-block:: terminal

$ composer update "symfony/*"
$ composer update "symfony/*" --with-all-dependencies

.. include:: /setup/_update_dep_errors.rst.inc

Expand Down
10 changes: 1 addition & 9 deletions setup/upgrade_patch.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,15 +8,7 @@ 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:

.. code-block:: terminal

$ composer update "symfony/*"

That's it! You should not encounter any backwards-compatibility breaks or
need to change anything else in your code. That's because when you started
your project, your ``composer.json`` included Symfony using a constraint
like ``^4.1``, where only the *last* version number will change when you
update.
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.

.. tip::

Expand Down