Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 5.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v4...v5)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: '5'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

…s/actions/checkout-5

Bump actions/checkout from 4 to 5

Bumps [actions/checkout](https://github.com/actions/checkout) from 5 to 6.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v5...v6)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

…s/actions/checkout-6

Bump actions/checkout from 5 to 6

…ng (GrahamCampbell)

This PR was merged into the 3.16-dev branch.

Discussion
----------

GitHub sometimes returns a 422 response in which the `errors` property is a plain string rather than an array of error objects, for example when creating a commit status for a commit that cannot be found. The exception thrower currently iterates over that property unconditionally, so instead of throwing a `ValidationFailedException` carrying the message from GitHub, it triggers a PHP warning about passing a string to `foreach`, which under most frameworks surfaces as an `ErrorException` and hides the real error. This change casts the property to an array before iterating, so a string is reported through the existing string handling branch, and adds a test case covering that response shape.

Commits
-------

754a9e8 Fix handling of 422 responses where errors is a string