chore(deps): bump the github-actions group with 3 updates

[dependabot]

Bumps the github-actions group with 3 updates: github/codeql-action/init, github/codeql-action/analyze and oasdiff/oasdiff-action/breaking.

Updates github/codeql-action/init from 4.37.7 to 4.37.8

Release notes

Sourced from github/codeql-action/init's releases.

v4.37.8

No user facing changes.

Changelog

Sourced from github/codeql-action/init's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.37.8 - 21 Aug 2026

No user facing changes.

4.37.7 - 13 Aug 2026

• Update default CodeQL bundle version to 2.26.3. #4085

4.37.6 - 04 Aug 2026

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

4.37.5 - 03 Aug 2026

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

4.37.4 - 29 Jul 2026

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

4.37.3 - 22 Jul 2026

No user facing changes.

4.37.2 - 21 Jul 2026

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

4.37.1 - 16 Jul 2026

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
• Update default CodeQL bundle version to 2.26.1. #4019

4.37.0 - 08 Jul 2026

• Update default CodeQL bundle version to 2.26.0. #3995
• In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

4.36.3 - 01 Jul 2026

... (truncated)

Commits

• db488dd Merge pull request #4102 from github/update-v4.37.8-9ee088e13
• 1845f5b Update changelog for v4.37.8
• 9ee088e Merge pull request #4080 from github/henrymercer/studious-giggle
• 1aef003 Address review feedback on overlay disk flags
• 508b83b Merge main into overlay minimum disk feature branch
• d97b342 Merge pull request #4098 from github/mbg/permission-error-as-configuration-error
• 47fa622 Make EACCES a ConfigurationError
• 45693cc Refactor ENOSPC check into isDiskConfigurationError function
• c2fd8f5 Merge pull request #4081 from github/mario-campos/version-cache-to-disk
• c56f48e Log unexpected conditions during caching CLI output
• Additional commits viewable in compare view

Updates github/codeql-action/analyze from 4.37.7 to 4.37.8

Release notes

Sourced from github/codeql-action/analyze's releases.

v4.37.8

No user facing changes.

Changelog

Sourced from github/codeql-action/analyze's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.37.8 - 21 Aug 2026

No user facing changes.

4.37.7 - 13 Aug 2026

• Update default CodeQL bundle version to 2.26.3. #4085

4.37.6 - 04 Aug 2026

• Changed the default filepath for the new remote file address format that was introduced in CodeQL Action 4.37.0 / 3.37.0 to .github/codeql-config.yml to align it with the suggested path that is used elsewhere. #4070

4.37.5 - 03 Aug 2026

• Fixed a bug where a network error while streaming the download of the CodeQL bundle could terminate the init Action instead of falling back to downloading the bundle before extracting it. #4061

4.37.4 - 29 Jul 2026

• This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
• Update default CodeQL bundle version to 2.26.2. #4051

4.37.3 - 22 Jul 2026

No user facing changes.

4.37.2 - 21 Jul 2026

• The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
• The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

4.37.1 - 16 Jul 2026

• Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
• Update default CodeQL bundle version to 2.26.1. #4019

4.37.0 - 08 Jul 2026

• Update default CodeQL bundle version to 2.26.0. #3995
• In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

4.36.3 - 01 Jul 2026

... (truncated)

Commits

• db488dd Merge pull request #4102 from github/update-v4.37.8-9ee088e13
• 1845f5b Update changelog for v4.37.8
• 9ee088e Merge pull request #4080 from github/henrymercer/studious-giggle
• 1aef003 Address review feedback on overlay disk flags
• 508b83b Merge main into overlay minimum disk feature branch
• d97b342 Merge pull request #4098 from github/mbg/permission-error-as-configuration-error
• 47fa622 Make EACCES a ConfigurationError
• 45693cc Refactor ENOSPC check into isDiskConfigurationError function
• c2fd8f5 Merge pull request #4081 from github/mario-campos/version-cache-to-disk
• c56f48e Log unexpected conditions during caching CLI output
• Additional commits viewable in compare view

Updates oasdiff/oasdiff-action/breaking from 0.1.12 to 0.1.13

Release notes

Sourced from oasdiff/oasdiff-action/breaking's releases.

v0.1.13

Highlights

Upgraded to oasdiff v1.29.1

All actions now run on oasdiff v1.29.1 (#194, #201).

include-checks is deprecated: use .oasdiff.yaml instead

oasdiff retired the optional-checks mechanism behind include-checks, so the input has been silently doing nothing. The actions no longer forward it to the CLI and instead emit a warning annotation explaining the replacement. Workflows that still pass the input keep working rather than failing on an unknown flag (#197).

To make a specific check fail the build, list it in a severity-levels file and point .oasdiff.yaml at it:

# .oasdiff.yaml
severity-levels: ./oasdiff-levels.txt
fail-on: ERR

# oasdiff-levels.txt
api-version-not-bumped    err

Anonymous delivery reporting for review comments

The breaking, changelog, and pr-comment actions now send oasdiff.com one anonymous event per run saying whether the review link was posted as a PR comment or fell back to the job summary, so the defaults can be improved. No repo, organization, or user identity is sent, failures never affect the run, and setting OASDIFF_INTERNAL=1 skips it entirely (#195).

Fixes

• A failed comparison no longer reads as a clean result. When oasdiff could not load or parse a spec, the breaking and diff actions failed the step but still wrote No breaking changes / No changes to the step output, job summary, and PR comment, and the validate action published findings=0 with all counts at zero for an unloadable spec. All three now stop as soon as the comparison fails, so anything reading the outputs, or running with continue-on-error, sees the failure instead of a clean report. Regression tests pin the behavior for each action (#199, thanks @​lucas-monteiro-g, who found this and opened #198 with a fix and a test fixture).

Full Changelog: oasdiff/oasdiff-action@v0.1.12...v0.1.13

Commits

• 2649ebe bump: oasdiff v1.29.1 (#201)
• 5ad1d21 Stop reporting a failed comparison as a clean result (#199)
• aac8c66 Stop pretending include-checks works, and point it at .oasdiff.yaml (#197)
• b803cbd report anonymously whether the review comment could be posted (#195)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud