Upgrading a Patch Version (e.g. 2.6.0 to 2.6.1)

Upgrading a Patch Version (e.g. 2.6.0 to 2.6.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:

$ composer update symfony/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 2.6.*, where only the last version number will change when you update.


It is recommended to update to a new patch version as soon as possible, as important bugs and security leaks may be fixed in these new releases.

Upgrading other Packages

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:

$ composer update


Beware, if you have some unspecific version constraints in your composer.json (e.g. dev-master), this could upgrade some non-Symfony libraries to new versions that contain backwards-compatibility breaking changes.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.