Bump MishaKav/pytest-coverage-comment from 1.11.2 to 1.12.2 in the github-actions group

[dependabot]

Bumps the github-actions group with 1 update: MishaKav/pytest-coverage-comment.

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

Release notes

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

v1.12.2

What's Changed

• bump dev dependencies: @types/node 26.4.0, @vercel/ncc 0.45.0, @vitest/coverage-v8 4.1.11, vitest 4.1.11, eslint 10.9.1, typescript-eslint 8.68.0 (#302)

Full Changelog: MishaKav/pytest-coverage-comment@v1.12.1...v1.12.2

v1.12.1

What's Changed

• 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

Full Changelog: MishaKav/pytest-coverage-comment@v1.12.0...v1.12.1

v1.12.0

What's Changed

• 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

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

Changelog

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

Pytest Coverage Comment 1.12.2

Release Date: 2026-09-01

Changes

• bump dev dependencies: @types/node 26.4.0, @vercel/ncc 0.45.0, @vitest/coverage-v8 4.1.11, vitest 4.1.11, eslint 10.9.1, typescript-eslint 8.68.0 (#302)

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

Commits

• 432ac90 Bump the npm-development group with 6 updates (#302)
• 1fcf8a5 fix: enforce GitHub's 65,536-character comment limit before posting (#301)
• f79b34a feat: show warning in comment when coverage report is too long (v1.12.0) (#300)
• 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

[github-actions]

Coverage Report •

File	Stmts	Miss	Branch	BrPart	Cover	Missing
TOTAL	641	19	160	9	97%

report-only-changed-files is enabled. No changed files were found in the coverage report :)