I just testing new features on symfony 2.1-BETA3. Few hours ago BETA4 has been released but I don't know how to update BETA3 to BETA4 using composer. In 2.0.x release notes Fabien said:
If you already have a project based on the Symfony Standard Edition 2.0.x, you can easily upgrade to 2.0.15 by getting the new deps and deps.lock files.
Have I replace my composer.lock file? What about my own requires like:
"package": "stof/doctrine-extensions-bundle",
"version": "dev-master",
"source-reference": "36356b158b74cb68f96dc0b657e8732422b9d5dd",
"commit-date": "1341954345"
To update to the latest versions, use the update command. This will fetch the latest matching versions (according to your composer. json file) and update the lock file with the new versions. Note: Composer will display a Warning when executing an install command if the composer.
Don't touch composer.lock
! Change composer.json
. If you are using the standard edition, you probably already have something like
"symfony/symfony": "2.1.*"
and
"minimum-stability": "dev"
in there. The later one means, that you allow dev packages to get installed. The first one means, that you want any 2.1.*
version. You can change it to
"symfony/symfony": "2.1.0-BETA4"
if you want, but the original 2.1.*
should be suffice right now. Now call
php composer.phar update
This will update composer.lock
too. Now you maybe must call (must say: I've forgotten it) call
php composer.phar install
to install the dependencies from composer.lock
.
In short:
# To install (maybe even after update)
$ php composer.phar install
# To update
$ php composer.phar update
# To add, remove or change dependencies
# edit composer.json
$ php composer.phar update
YOu never need to touch composer.lock
yourself and you shouldn't to avoid side effects of composer.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With