Skip to content

Comments

Bump MishaKav/pytest-coverage-comment from 1.2.0 to 1.3.0#51

Open
dependabot[bot] wants to merge 1 commit intoGR-Devfrom
dependabot/github_actions/MishaKav/pytest-coverage-comment-1.3.0
Open

Bump MishaKav/pytest-coverage-comment from 1.2.0 to 1.3.0#51
dependabot[bot] wants to merge 1 commit intoGR-Devfrom
dependabot/github_actions/MishaKav/pytest-coverage-comment-1.3.0

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Feb 22, 2026

Bumps MishaKav/pytest-coverage-comment from 1.2.0 to 1.3.0.

Release notes

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

v1.2.1

What's Changed

  • fix fork PR permission error with specific guidance for pull_request_target (#243)
  • bump production deps: @actions/core to 2.0.3, @actions/github to 8.0.1
  • bump dev deps: eslint to 10.0.1, globals to 17.3.0, prettier to 3.8.1
  • upgrade action runtime from node20 to node24
  • fix comment-too-long code path not replacing HTML with shorter report

Full Changelog: MishaKav/pytest-coverage-comment@v1.2.0...v1.2.1

Changelog

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

Pytest Coverage Comment 1.3.0

Release Date: 2026-02-21

Changes

  • feat: add XML coverage support in multiple-files mode (#200), thanks to @​hayes0724 for contribution
  • multiple-files input now auto-detects XML coverage files by .xml extension
  • allows mixing TXT and XML coverage formats in the same multi-file report (useful for monorepos)
  • add safety check for XML coverage structure to prevent runtime errors

Pytest Coverage Comment 1.2.1

Release Date: 2026-02-21

Changes

  • fix fork PR permission error with specific guidance for pull_request_target (#243)
  • bump production deps: @actions/core to 2.0.3, @actions/github to 8.0.1
  • bump dev deps: eslint to 10.0.1, globals to 17.3.0, prettier to 3.8.1
  • upgrade action runtime from node20 to node24
  • fix comment-too-long code path not replacing HTML with shorter report
Commits

Dependabot compatibility score

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [MishaKav/pytest-coverage-comment](https://github.com/mishakav/pytest-coverage-comment) from 1.2.0 to 1.3.0.
- [Release notes](https://github.com/mishakav/pytest-coverage-comment/releases)
- [Changelog](https://github.com/MishaKav/pytest-coverage-comment/blob/main/CHANGELOG.md)
- [Commits](MishaKav/pytest-coverage-comment@v1.2.0...v1.3.0)

---
updated-dependencies:
- dependency-name: MishaKav/pytest-coverage-comment
  dependency-version: 1.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Feb 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants