build: bump the all-actions group with 2 updates

[dependabot]

Bumps the all-actions group with 2 updates: github/codeql-action and MishaKav/pytest-coverage-comment.

Updates github/codeql-action from 4.37.3 to 4.37.9

Release notes

Sourced from github/codeql-action's releases.

v4.37.9

• Update default CodeQL bundle version to 2.26.4. #4106

v4.37.8

No user facing changes.

v4.37.7

• Update default CodeQL bundle version to 2.26.3. #4085

v4.37.6

• 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

v4.37.5

• 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

v4.37.4

• 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

Changelog

Sourced from github/codeql-action's changelog.

4.37.9 - 26 Aug 2026

• Update default CodeQL bundle version to 2.26.4. #4106

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

Commits

• cdf488f Merge pull request #4107 from github/update-v4.37.9-920ba7cd1
• 7243f38 Update changelog for v4.37.9
• 920ba7c Merge pull request #4106 from github/update-bundle/codeql-bundle-v2.26.4
• ecfa6e1 Add changelog note
• adcdf4a Update default bundle to codeql-bundle-v2.26.4
• 486fec2 Merge pull request #4099 from github/update-supported-enterprise-server-versions
• 134624c Merge pull request #4101 from github/dependabot/npm_and_yarn/npm-minor-457d82...
• ff43db8 Merge pull request #4103 from github/mergeback/v4.37.8-to-main-db488dde
• 4605e03 Rebuild
• 099c869 Update changelog and version after v4.37.8
• Additional commits viewable in compare view

Updates MishaKav/pytest-coverage-comment from 1.10.0 to 1.11.2

Release notes

Sourced from MishaKav/pytest-coverage-comment's releases.

v1.11.2

What's Changed

• improve the comment message when report-only-changed-files is enabled and none of the changed files appear in the coverage report — it now says "No changed files were found in the coverage report" instead of the misleading "No files were changed during this commit" (#296), thanks to @​mschoettle for contribution

Full Changelog: MishaKav/pytest-coverage-comment@v1.11.1...v1.11.2

v1.11.1

What's Changed

• bump undici from 6.27.0 to 6.28.0 (fixes three security vulnerabilities)
• Fix badge creation on Dependabot and fork PRs [skip ci] by @​MishaKav in MishaKav/pytest-coverage-comment#295

Full Changelog: MishaKav/pytest-coverage-comment@v1.11.0...v1.11.1

v1.11.0

What's Changed

• add show-failed-tests input that lists failed tests (up to max-failed-tests) in the comment as a collapsible block with the test name linked to its file, a short failure reason and the pytest output
• add max-failed-tests input to cap the number of shown failed tests (30 by default, in total across all junit files, shared with multiple-files mode)
• add failedTestsHtml output with the rendered block, empty when the option is disabled or all tests pass

Test Results

Tests	Skipped	Failures	Errors	Time
4	0 💤	4 ❌	0 🔥	0.122s ⏱️

def test_wrong_title():
        # genuine failing assertion with a string diff
        post = get_post(1)
>       assert post["title"] == "my first post"
E       AssertionError: assert 'first post' == 'my first post'
E
E         - my first post
E         ? ---
E         + first post

def test_fetch_latest_post_times_out():
        # genuine timeout raised by the module under test
</tr></table> 

... (truncated)

Changelog

Sourced from MishaKav/pytest-coverage-comment's changelog.

Changelog of the Pytest Coverage Comment

Pytest Coverage Comment 1.12.1

Release Date: 2026-08-30

Changes

• fix a rare case where the comment was still too long and failed to post — it's now always truncated to fit GitHub's limit (#301), fixes #299

Pytest Coverage Comment 1.12.0

Release Date: 2026-08-30

Changes

• show a warning inside the comment itself when it's too long (over 65,536 characters) and the detailed coverage report gets dropped — previously the report silently disappeared and the reason was only visible in the job log. The warning links to the job log, which lists the ways to reduce the comment size (#298), thanks to @​mschoettle for contribution

Pytest Coverage Comment 1.11.2

Release Date: 2026-08-26

Changes

• improve the comment message when report-only-changed-files is enabled and none of the changed files appear in the coverage report — it now says "No changed files were found in the coverage report" instead of the misleading "No files were changed during this commit" (#296), thanks to @​mschoettle for contribution

Pytest Coverage Comment 1.11.1

Release Date: 2026-08-22

Changes

• bump undici from 6.27.0 to 6.28.0 (fixes three security vulnerabilities)

Pytest Coverage Comment 1.11.0

Release Date: 2026-08-02

Changes

• add show-failed-tests input that lists failed tests (up to max-failed-tests) in the comment as a collapsible block with the test name linked to its file, a short failure reason and the pytest output (#293), requested in #26
• add max-failed-tests input to cap the number of shown failed tests (30 by default, in total across all junit files, shared with multiple-files mode) (#293)
• add failedTestsHtml output with the rendered block, empty when the option is disabled or all tests pass (#293)

Pytest Coverage Comment 1.10.1

Release Date: 2026-08-01

Changes

... (truncated)

Commits

• ce64cfb Improve message when no changed files found in coverage report (#297)
• d46d9d5 Bump undici from 6.27.0 to 6.28.0 (#294)
• 67e0872 ci: skip badge step in live-test when the gist secret is unavailable (#295)
• 09c28b6 Add failed tests report to JUnit output (show-failed-tests) (#293)
• 96fbda6 chore: release v1.10.1 (#292)
• 4f3ea85 Bump brace-expansion from 5.0.6 to 5.0.8 (#287)
• 62e8522 Bump the npm-development group with 6 updates (#290)
• 481dcf4 Bump schneegans/dynamic-badges-action from 1.8.0 to 1.9.0 (#289)
• 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