4.0.0

What's Changed

• chore: Bump actions/cache from 4.2.4 to 5.0.3 by @dependabot[bot] in #278

  This necessitates a new major version because actions/cache v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1. This is a breaking change for anyone using self-hosted runners.

Full Changelog: 3.2.1...4.0.0

3.2.1

What's Changed

• Fix missing cache key hash of composer.json (and composer.lock), as reported in #277.

Full Changelog: 3.2.0...3.2.1

3.2.0

What's Changed

• Pin cache action version by @saibotk in #271

New Contributors

• @saibotk made their first contribution in #271

Full Changelog: 3.1.1...3.2.0

3.1.1

What's Changed

• Use the value of the COMPOSER environment 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

What's Changed

• fix: Improve composer.lock behavior with ignore-cache by @flagbrad in #260

New Contributors

• @flagbrad made their first contribution in #260

Full Changelog: 3.0.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-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)