Bump ramsey/composer-install from 2 to 3

[dependabot]

Bumps ramsey/composer-install from 2 to 3.

Release notes

Sourced from ramsey/composer-install's releases.

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

... (truncated)

Commits

• 0f18aec Update examples in README to v3
• 57532f8 Update cache action runner (#252)
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot]

The following labels could not be found: dependencies.

[spatie-bot]

Dear contributor,

because this pull request seems to be inactive for quite some time now, I've automatically closed it. If you feel this pull request deserves some attention from my human colleagues feel free to reopen it.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.