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-file input that forces a build failure if a composer.lock file is not present. (#251)

Fixed

• Add --working-dir when looking up Composer's cache directory. This fixes "File composer.json could not be found in the current directory" errors when running composer 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)

2.2.0

Added

• Implement custom-cache-suffix option 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-output command for GitHub's recommended approach for output (#238)

2.1.0

Added

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

2.0.5

Fixed

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

2.0.4

Fixed

• Fix typo in variable name

2.0.3

Fixed

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

2.0.2

Fixed

• Fix case when values other than locked, highest, or lowest are passed for dependency_versions. In these cases, we always default to locked.