Releases: ramsey/composer-install
Releases · ramsey/composer-install
3.1.1
What's Changed
- Use the value of the
COMPOSERenvironment variable if it exists; fixes #264
Full Changelog: 3.1.0...3.1.1
3.1.0
What's Changed
- ✨ Add new composer-filename option by @badasukerubin in #261
- Add instructions on how to use the automatic GHA token by @Jean85 in #263
New Contributors
- @badasukerubin made their first contribution in #261
Full Changelog: 3.0.1...3.1.0
3.0.1
3.0.0
Changed
-
Update actions/cache to v4 to avoid deprecation notices.
This requires a new major version because actions/cache requires Node.js 20, which could cause backwards-compatibility breaks for any projects that require earlier versions of Node.js.
For more details, see the discussion on #252.
2.3.1
Fixed
- Removed upgrade to cache action runner v4 to avoid potential backwards-compatibility issues that might arise when using self-hosted runners that use Node.js 16 instead of version 20. For more details, see the discussion here: #252.
To avoid the actions/cache deprecation notices, upgrade to @v3 or @3.0.0.
2.3.0
Added
- Add new
require-lock-fileinput that forces a build failure if acomposer.lockfile is not present. (#251)
Fixed
- Add
--working-dirwhen looking up Composer's cache directory. This fixes "Filecomposer.jsoncould not be found in the current directory" errors when runningcomposer installin sub-directories or other non-standard locations. (#225, #233, #246, #247) - Update cache action runner to v4 to avoid deprecation notices. (#252, #253, #254)
2.2.0
Added
- Implement
custom-cache-suffixoption to allow projects to provide their own cache-busting strategies without defining full custom cache keys (#239)
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.