GH Actions: Bump the action-runners group across 1 directory with 2 updates

[dependabot]

Bumps the action-runners group with 2 updates in the / directory: shivammathur/setup-php and eps1lon/actions-label-merge-conflict.

Updates shivammathur/setup-php from 2.37.0 to 2.37.2

Release notes

Sourced from shivammathur/setup-php's releases.

2.37.2

Changelog

• Fixed macOS setup by marking shivammathur/php and shivammathur/extensions as trusted taps.

• Switched to Visual Studio 18 (vs18) builds for PHP 8.6 on Windows.

• Improved looking up environment variables.

• Tightened security in internal GitHub action workflows.

• Updated Node.js dependencies.

For the complete list of changes, please refer to the Full Changelog

2.37.1

Changelog

Security Updates

• Fixed shell command escaping and PHP version input validation. (GHSA-pqwm-q9pv-ph8r / CVE-2026-46420)

[!NOTE] This can affect workflows that pass values from users or pull requests to setup-php, for example from comments, dispatch inputs, PR titles/branches, generated matrices, or files such as .php-version and composer.json. Be especially careful with pull_request_target workflows that use any value from the pull request. Workflows that only use fixed trusted values are not expected to be affected, but updating to 2.37.1 is recommended.

• Fixed GitHub auth handling for Composer versions affected by GHSA-f9f8-rm49-7jv2. It should now skip configuring GitHub OAuth if affected Composer versions are installed and show a warning to upgrade. (GHSA-5wxr-w449-57cm / CVE-2026-45793)

[!NOTE]
This only affects workflows where the composer version is pinned like composer:2.9.7, workflows that do not pin the version or use composer:v2 are not affected as those get automatic updates. In case you pin the version, it is highly recommended to upgrade and have automation to do such timely upgrades in your workflows.

Fixes and Improvements

• Fixed support for phalcon on Windows.

• Fixed restoring tools when using cached using previous runs.

• Improved enabling gearman extension on Linux.

• Fixed fallback when installing PhpManager and VcRedist modules on Windows.

• Fixed parsing extension inputs with backslash line continuation.

• Improved workflow examples

  • Added workflow examples for Drupal 11 composer-managed projects and WordPress plugins.

... (truncated)

Commits

• f3e473d Bump version to 2.37.2
• 8be473c Trust brew taps
• 083d523 Bump the github-actions group with 2 updates (#1085)
• a919ff5 Update FUNDING.yml
• deb2299 Harden GitHub Actions workflows
• 5825be4 Harden environment lookup
• 8d45593 Add CODEOWNERS
• ba8d163 Update PHP versions in SECURITY.md
• 7c071df Bump version to 2.37.1
• eeef37e GHSA-pqwm-q9pv-ph8r - Fix CWE-78 [skip ci]
• Additional commits viewable in compare view

Updates eps1lon/actions-label-merge-conflict from 3.0.3 to 3.1.0

Release notes

Sourced from eps1lon/actions-label-merge-conflict's releases.

v3.1.0

What's Changed

• Add better permissions defaults for the example by @​oliviertassinari in eps1lon/actions-label-merge-conflict#151
• Update Node.js to 24 by @​oliviertassinari in eps1lon/actions-label-merge-conflict#152
• release: 3.1.0 by @​eps1lon in eps1lon/actions-label-merge-conflict#153

New Contributors

• @​oliviertassinari made their first contribution in eps1lon/actions-label-merge-conflict#151

Full Changelog: eps1lon/actions-label-merge-conflict@v3.0.3...v3.1.0

Changelog

Sourced from eps1lon/actions-label-merge-conflict's changelog.

Changelog

3.1.0

• Update Node.js to 24 (#152)

3.0.3

• Ensure outputs is populated (#136)

3.0.2

• Handle error when label is not available (part 2) (#126)

3.0.1

• Handle error when label is not available (#123)

3.0.0

• Update to node20 (#115)

2.1.0

• Address set-output deprecation (#92 by @​NotMyFault)
• Fix CVE-2022-35954 (#92 by @​NotMyFault)

2.0.1

• Improve retry logic (#31 by @​eps1lon)

2.0.0

• Only update PRs based off of the branch in the push event Previously we checked every open PR. Since a push to a branch can only create merge conflicts with that branch we can limit the set of checked PRs. This should help repositories with lots of PRs targetting different branches with rate limiting.
• Only leave comments if the dirtyLabel was added or removed

1.4.0

• Allow warning only if secrets aren't available (#22 by @​baywet)
• Remove requirement for removeOnDirtyLabel (#21 by @​baywet)

1.3.0

• set PRs and their dirty state as output (#17 by @​baywet)

Commits

• 0273be7 release: 3.1.0 (#153)
• 9d4606b Update Node.js to 24 (#152)
• 62d0db0 docs: Add better permissions defaults for the example (#151)
• See full diff in compare view

[jrfnl]

@dependabot rebase