Bump ramsey/composer-install from 2 to 3 #5

Merged

dependabot[bot] merged 1 commit from dependabot/github_actions/ramsey/composer-install-3 into main

2024-11-12 10:02:09 +00:00

dependabot[bot] commented

2024-11-11 15:16:49 +00:00

(Migrated from github.com)

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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)

Bumps [ramsey/composer-install](https://github.com/ramsey/composer-install) from 2 to 3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/ramsey/composer-install/releases">ramsey/composer-install's releases</a>.</em></p> <blockquote> <h2>3.0.0</h2> <h2>Changed</h2> <ul> <li> <p>Update actions/cache to v4 to avoid deprecation notices.</p> <p>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.</p> <p>For more details, see the discussion on <a href="https://redirect.github.com/ramsey/composer-install/pull/252">#252</a>.</p> </li> </ul> <h2>2.3.1</h2> <h2>Fixed</h2> <ul> <li>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: <a href="https://redirect.github.com/ramsey/composer-install/pull/252">#252</a>.</li> </ul> <p><strong>To avoid the actions/cache deprecation notices, upgrade to <code>@v3</code> or <code>@3.0.0</code>.</strong></p> <h2>2.3.0</h2> <h2>Added</h2> <ul> <li>Add new <code>require-lock-file</code> input that forces a build failure if a <code>composer.lock</code> file is not present. (<a href="https://redirect.github.com/ramsey/composer-install/pull/251">#251</a>)</li> </ul> <h2>Fixed</h2> <ul> <li>Add <code>--working-dir</code> when looking up Composer's cache directory. This fixes "File <code>composer.json</code> could not be found in the current directory" errors when running <code>composer install</code> in sub-directories or other non-standard locations. (<a href="https://redirect.github.com/ramsey/composer-install/issues/225">#225</a>, <a href="https://redirect.github.com/ramsey/composer-install/pull/233">#233</a>, <a href="https://redirect.github.com/ramsey/composer-install/issues/246">#246</a>, <a href="https://redirect.github.com/ramsey/composer-install/pull/247">#247</a>)</li> <li>Update cache action runner to v4 to avoid deprecation notices. (<a href="https://redirect.github.com/ramsey/composer-install/pull/252">#252</a>, <a href="https://redirect.github.com/ramsey/composer-install/issues/253">#253</a>, <a href="https://redirect.github.com/ramsey/composer-install/pull/254">#254</a>)</li> </ul> <h2>2.2.0</h2> <h2>Added</h2> <ul> <li>Implement <code>custom-cache-suffix</code> option to allow projects to provide their own cache-busting strategies without defining full custom cache keys (<a href="https://redirect.github.com/ramsey/composer-install/pull/239">#239</a>)</li> </ul> <h2>2.1.1</h2> <h2>Fixed</h2> <ul> <li>Swap uses of deprecated <code>set-output</code> command for <a href="https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/">GitHub's recommended approach for output</a> (<a href="https://redirect.github.com/ramsey/composer-install/pull/238">#238</a>)</li> </ul> <h2>2.1.0</h2> <h2>Added</h2> <ul> <li>Force the use of <code>composer update</code> if a lock file is not present, avoiding the warning that appears when running <code>composer install</code> without a lock file.</li> </ul> <h2>2.0.5</h2> <h2>Fixed</h2> <ul> <li>Don't error on out-of-sync lock file (<a href="https://redirect.github.com/ramsey/composer-install/issues/206">#206</a>, <a href="https://redirect.github.com/ramsey/composer-install/issues/213">#213</a>)</li> <li>Do not append empty restore key (<a href="https://redirect.github.com/ramsey/composer-install/issues/216">#216</a>)</li> </ul> <h2>2.0.4</h2> <h2>Fixed</h2>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ramsey/composer-install/commit/0f18aec461938c57720faaf2dba4421bf698cf42"><code>0f18aec</code></a> Update examples in README to v3</li> <li><a href="https://github.com/ramsey/composer-install/commit/57532f8be5bda426838819c5ee9afb8af389d51a"><code>57532f8</code></a> Update cache action runner (<a href="https://redirect.github.com/ramsey/composer-install/issues/252">#252</a>)</li> <li>See full diff in <a href="https://github.com/ramsey/composer-install/compare/v2...v3">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=ramsey/composer-install&package-manager=github_actions&previous-version=2&new-version=3)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details>

dependabot[bot] commented

2024-11-11 15:16:50 +00:00

(Migrated from github.com)

The following labels could not be found: dependencies.

The following labels could not be found: `dependencies`.