Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Adding a guide about upgrading #4611

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

Closed
wants to merge 6 commits into from
Closed
Changes from 1 commit
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
Prev Previous commit
Next Next commit
Basically copying a section about upgrading other libraries down into…
… the minor version section
  • Loading branch information
weaverryan committed Jan 3, 2015
commit 2bee7cc013a5ee00f64cd293b4291f1c0561c528
20 changes: 14 additions & 6 deletions 20 cookbook/upgrading.rst
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ safely by running:

$ composer update

But beware. If you have some bad version constraints in your ``composer.json``,
But beware. If you have some bad `version constraints`_ in your ``composer.json``,
(e.g. ``dev-master``), then this could upgrade some non-Symfony libraries
to new versions that contain backwards-compatibility breaking changes.

Expand Down Expand Up @@ -83,11 +83,17 @@ Next, use Composer to download new versions of the libraries:

$ composer update symfony/symfony

Updating a minor version like this should *not* cause any dependency issues,
though it's always possible that an outside library or bundle you're using
didn't support this new version of Symfony at the version you have of that
library. In that case, consult the library: you may need to modify its version
in ``composer.json`` and run a full ``composer update``.
You may also want to upgrade the rest of your libraries. If you've done a
good job with your version constraints in ``composer.json``, you can do this
safely by running:

.. code-block:: bash

$ composer update

But beware. If you have some bad `version constraints`_ in your ``composer.json``,
(e.g. ``dev-master``), then this could upgrade some non-Symfony libraries
to new versions that contain backwards-compatibility breaking changes.

.. _`upgrade-minor-symfony-code`:

Expand Down Expand Up @@ -130,3 +136,5 @@ that you might need to make in your project.
.. _`UPGRADE-2.5`: https://github.com/symfony/symfony/blob/2.5/UPGRADE-2.5.md
.. _`UPGRADE-2.6`: https://github.com/symfony/symfony/blob/2.6/UPGRADE-2.6.md
.. _`Symfony Repository`: https://github.com/symfony/symfony
.. _`Composer Package Versions`: https://getcomposer.org/doc/01-basic-usage.md#package-versions
.. _`version constraints`: https://getcomposer.org/doc/01-basic-usage.md#package-versions
Morty Proxy This is a proxified and sanitized view of the page, visit original site.