chore(deps): update ramsey/composer-install action to v4

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
ramsey/composer-install	action	major	v1 → 4.0.0

---

Release Notes

ramsey/composer-install (ramsey/composer-install)

v4.0.0

Compare Source

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: ramsey/composer-install@3.2.1...4.0.0

v3.2.1

Compare Source

What's Changed

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

Full Changelog: ramsey/composer-install@3.2.0...3.2.1

v3.2.0

Compare Source

What's Changed

• Pin cache action version by @​saibotk in #​271

New Contributors

• @​saibotk made their first contribution in #​271

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

v3.1.1

Compare Source

What's Changed

• Use the value of the COMPOSER environment variable if it exists; fixes #​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 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: 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 in #​260

New Contributors

• @​flagbrad made their first contribution in #​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 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)

v2.2.0

Compare Source

Added

• Implement custom-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 deprecated set-output command for GitHub's recommended approach for output (#​238)

v2.1.0

Compare Source

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.

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 than locked, highest, or lowest are passed for dependency_versions. In these cases, we always default to locked.

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.
• Validate composer.json and emit error message if it does not validate.

v2.0.0

Compare Source

Added

• Use --prefer-stable with 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

• Fix case where working-directory did not run composer install in the correct working directory (#​187)
• Fix problems with retrieving cache with parallel builds (#​161, #​152)
• Fix problems restoring from cache on Windows (#​79)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.94%. Comparing base (791b1aa) to head (e9075f9).

Additional details and impacted files

@@           Coverage Diff           @@
##            7.0.x     #181   +/-   ##
=======================================
  Coverage   94.94%   94.94%           
=======================================
  Files           3        3           
  Lines         257      257           
=======================================
  Hits          244      244           
  Misses         13       13           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.