meta: bump MishaKav/jest-coverage-comment from 1.0.25 to 1.0.26

Open dependabot[bot] opened this issue 1 year ago • 1 comments

Bumps MishaKav/jest-coverage-comment from 1.0.25 to 1.0.26.

Release notes

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

v1.0.26

What's Changed

Handle case when testsuites is not the root element of the JUnit xml file, thanks to @JakeFDev for contribution in MishaKav/jest-coverage-comment#86

Full Changelog: https://github.com/MishaKav/jest-coverage-comment/compare/v1.0.25...v1.0.26

Changelog

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

Changelog of the Jest Coverage Comment

Jest Coverage Comment 1.0.26

Release Date: 2024-04-30

Changes

Handle case when testsuites is not the root element of the JUnit xml file, thanks to @JakeFDev for contribution

Jest Coverage Comment 1.0.25

Release Date: 2024-01-30

Changes

Change node16 to node20, thanks to @kagankan for contribution

Jest Coverage Comment 1.0.24

Release Date: 2023-11-23

Changes

Take right serverUrl in non github.com environments like selfhosted github, e.g. link to lines uses then the correct link, thanks to @c0un7-z3r0 for contribution

Jest Coverage Comment 1.0.23

Release Date: 2023-03-13

Changes

Remove summary error in annotations when provide one of junitxml-path / coverage-path / multiple-files / multiple-junitxml-files and not provide coverage-summary-path which have default value

Jest Coverage Comment 1.0.22

Release Date: 2023-01-07

Changes

Support pull_request_target event to add comments, thanks to @chirag-madlani for contribution

Jest Coverage Comment 1.0.21

Release Date: 2022-12-03

Changes

Support matrix with individual comments. When you run in a matrix, and you want that every job will post a comment, you can use the unique-id-for-comment: ${{ matrix.node-version }}. This will post a comment for every job, and will update them on every run.

... (truncated)

Commits

434e6d2 Fix root element at junit (#86)
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 merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@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)

May 01 '24 17:05 dependabot[bot]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
nodejs-org	⬜️ Ignored (Inspect)	Visit Preview	May 1, 2024 5:34pm

May 01 '24 17:05 vercel[bot]