I am trying to install a specific version of a package using Composer. I tried composer install and composer require but they are installing the latest version of the package. What if I want an older version?
-
have a read on this answer stackoverflow.com/questions/15212381/…Anastasis– Anastasis2016-12-01 15:18:52 +00:00Commented Dec 1, 2016 at 15:18
Add a comment
|
7 Answers
composer require vendor/package:version
for example:
composer require refinery29/test-util:0.10.2
2 Comments
free2idol1
composer require vendor/package:version --with-all-dependencies to make sure all of its dependency will be updated.
tinystone
with zsh (instead of bash), I need to use quotation marks just to escape
^ character eg. composer require "fakerphp/faker:^1.0"Add double quotes to use "^" caret operator in version number.
composer require middlewares/whoops "^0.4"
4 Comments
x-yuri
I don't see a point in time where you could pass package name and version as two separate arguments.
bryonbean
@x-yuri passing package name and version as separate arguments works for me using composer 1.5.1
Rich Court
While technically this isn't the "correct" answer for the OP's question, this is probably more useful for most people.
Dean Or
If you're using PowerShell and Git for Windows the caret needs to be escaped twice: "^^^^0.4" or just use Git Bash or cmd.exe. Ref: stackoverflow.com/questions/9600549/…
As @alucic mentioned, use:
composer require vendor/package:version
or you can use:
composer update vendor/package:version
You should probably review this StackOverflow post about differences between composer install and composer update.
Related to question about version numbers, you can review Composer documentation on versions, but here in short:
- Tilde Version Range (~) - ~1.2.3 is equivalent to >=1.2.3 <1.3.0
- Caret Version Range (^) - ^1.2.3 is equivalent to >=1.2.3 <2.0.0
So, with Tilde you will get automatic updates of patches but minor and major versions will not be updated. However, if you use Caret you will get patches and minor versions, but you will not get major (breaking changes) versions.
Tilde Version is considered a "safer" approach, but if you are using reliable dependencies (well-maintained libraries) you should not have any problems with Caret Version (because minor changes should not be breaking changes.
1 Comment
Berend de Boer
The
composer update vendor/package:version won't work.just use php composer.phar require
For example :
php composer.phar require doctrine/mongodb-odm-bundle 3.0
Also available with install.
https://getcomposer.org/doc/03-cli.md#require https://getcomposer.org/doc/03-cli.md#install
2 Comments
mindplay.dk
For the record, adding custom constraints is not available with
install - only with require. If you were hoping to switch to a specific version and check-in your composer.lock file, you can, but you'd have to use composer require and then revert the change to composer.json afterwards.x-yuri
Version as a separate argument? Was that ever available?
Suppose you want to install Laravel Collective. It's currently at version 6.x but you want version 5.8. You can run the following command:
composer require "laravelcollective/html":"^5.8.0"
A good example is shown here in the documentation: https://laravelcollective.com/docs/5.5/html
1 Comment
Nico Haase
Please share more details - the version constraint
^5.8.0 would not restrict Composer to use a specific version, but still allow multiple versions to be installedIn your composer.json, you can put:
{
"require": {
"vendor/package": "version"
}
}
then run composer install or composer update from the directory containing composer.json. Sometimes, for me, composer is hinky, so I'll start with composer clear-cache; rm -rf vendor; rm composer.lock before composer install to make sure it's getting fresh stuff.
Of course, as the other answers point out you can run the following from the terminal:
composer require vendor/package:version
And on versioning:
- Composer's official versions article
- Ecosia Search
Comments
I tried to require a development branch from a different repository and not the latest version and I had the same issue and non of the above worked for me :(
after a while I saw in the documentation that in cases of dev branch you need to require with a 'dev-' prefix to the version and the following worked perfectly.
composer require [vendorName]/[packageName]:dev-[gitBranchName]
