Releases: ramsey/composer-install
Releases · ramsey/composer-install
Release list
2.1.1
Fixed
- Swap uses of deprecated
set-outputcommand for GitHub's recommended approach for output (#238)
2.1.0
Added
- Force the use of
composer updateif a lock file is not present, avoiding the warning that appears when runningcomposer installwithout a lock file.
2.0.5
2.0.4
Fixed
- Fix typo in variable name
2.0.3
2.0.2
Fixed
- Fix case when values other than
locked,highest, orlowestare passed fordependency_versions. In these cases, we always default tolocked.
2.0.1
Fixed
- Fix case where cache keys might collide if using more than one working directory on a project.
- Improve error handling and reporting.
- Validate
composer.jsonand emit error message if it does not validate.
2.0.0
Added
- Use
--prefer-stablewith lowest dependencies (#178) - Allow use of a custom cache key (#167)
- Allow ability to ignore the cache
Changed
- Switch to a composite action from a JavaScript action
Fixed
1.3.0
- Support passing
--working-diras part ofcomposer-options
1.2.0
- Support Composer working-directory option for when
composer.jsonis in a non-standard location. - Add operating system name to the cache key.