crc-org / crc

CRC is a tool to help you run containers. It manages a local OpenShift 4.x cluster, Microshift or a Podman VM optimized for testing and development purposes
https://crc.dev
Apache License 2.0
1.26k stars 242 forks source link

build(deps): bump mikepenz/action-junit-report from 4 to 5 #4430

Closed dependabot[bot] closed 2 weeks ago

dependabot[bot] commented 2 weeks ago

Bumps mikepenz/action-junit-report from 4 to 5.

Release notes

Sourced from mikepenz/action-junit-report's releases.

v5

  • no changes

v5.0.0-rc01

🚀 Features

  • Improve parsing logic for nested suites
  • Configuration to enable grouping by TestSuite in the Detail Summary

💬 Other

  • Slight code cleanup

Contributors:

v5.0.0-b01

🚀 Features

  • Upgrade dependencies to latest major version
  • Add new API to skip annotations all-to-gether
  • Introduce flag to fail_on_parse_error

Contributors:

v5.0.0-a03

🚀 Features

  • Improve transformer performance
  • Provide optimised class detection skipping globber if not required

🐛 Fixes

  • Require pull_request trigger to attach comment

📦 Dependencies

... (truncated)

Commits
  • ec3a351 Merge pull request #1225 from mikepenz/feature/grouped_summary
  • b317015 - html formatting
  • 58833a9 - look to further modify formatting
  • 11d2c3e - update tests
  • bc02967 - further improve table format, remove obsolete first column
  • d9c3594 - adjust table structure
  • cfb2e06 - add grouping and comment for nested report
  • 9cc197e - fix group header (no merged cells possible)
  • 0d45d52 - update test
  • dda3b1e - introduce ability to group the test detailed summary
  • Additional commits viewable in compare view


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 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 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)
openshift-ci[bot] commented 2 weeks ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign gbraad for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/crc-org/crc/blob/main/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
openshift-ci[bot] commented 2 weeks ago

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a crc-org member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.