v3.1.1

Compare Source

What's Changed

• Use the value of theCOMPOSER environment variable if it exists; fixeshttps://github.com/ramsey/composer-install/pull/264

Full Changelog:ramsey/composer-install@3.1.0...3.1.1

v3.1.0

Compare Source

What's Changed

• ✨ Add new composer-filename option by@​badasukerubin inhttps://github.com/ramsey/composer-install/pull/261
• Add instructions on how to use the automatic GHA token by@​Jean85 inhttps://github.com/ramsey/composer-install/pull/263

New Contributors

• @​badasukerubin made their first contribution inhttps://github.com/ramsey/composer-install/pull/261

Full Changelog:ramsey/composer-install@3.0.1...3.1.0

v3.0.1

Compare Source

What's Changed

• fix: Improve composer.lock behavior with ignore-cache by@​flagbrad inhttps://github.com/ramsey/composer-install/pull/260

New Contributors

• @​flagbrad made their first contribution inhttps://github.com/ramsey/composer-install/pull/260

Full Changelog:ramsey/composer-install@3.0.0...3.0.1

v3.0.0

Compare Source

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.

v2.3.1

Compare Source

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.

v2.3.0

Compare Source

Added

• Add newrequire-lock-file input that forces a build failure if acomposer.lock file is not present. (#​251)

Fixed

• Add--working-dir when looking up Composer's cache directory. This fixes "Filecomposer.json could not be found in the current directory" errors when runningcomposer install in sub-directories or other non-standard locations. (#​225,#​233,#​246,#​247)
• Update cache action runner to v4 to avoid deprecation notices. (#​252,#​253,#​254)

v2.2.0

Compare Source

Added

• Implementcustom-cache-suffix option to allow projects to provide their own cache-busting strategies without defining full custom cache keys (#​239)

v2.1.1

Compare Source

Fixed

• Swap uses of deprecatedset-output command forGitHub's recommended approach for output (#​238)

v2.1.0

Compare Source

Added

• Force the use ofcomposer update if a lock file is not present, avoiding the warning that appears when runningcomposer install without a lock file.

v2.0.5

Compare Source

Fixed

• Don't error on out-of-sync lock file (#​206,#​213)
• Do not append empty restore key (#​216)

v2.0.4

Compare Source

Fixed

• Fix typo in variable name

v2.0.3

Compare Source

Fixed

• Convert GitHub Action notices to debug messages (#​211)
• Ensure compatibility with Composer 1.x (#​209,#​210)

v2.0.2

Compare Source

Fixed

• Fix case when values other thanlocked,highest, orlowest are passed fordependency_versions. In these cases, we always default tolocked.

v2.0.1

Compare Source

Fixed

• Fix case where cache keys might collide if using more than one working directory on a project.
• Improve error handling and reporting.
• Validatecomposer.json and emit error message if it does not validate.