Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update reportgenerator to v5.1.17 #936

Merged
merged 1 commit into from
Feb 9, 2023
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 9, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
ReportGenerator nuget patch 5.1.16 -> 5.1.17
dotnet-reportgenerator-globaltool nuget patch 5.1.16 -> 5.1.17

Release Notes

danielpalme/ReportGenerator

v5.1.17: ReportGenerator_5.1.17

This release requires .NET 4.7 or .NET Core 3.1/5.x/6.x/7.x.

Changes:
  • Fix: #​536: Improved support for C code in Visual Studio coverage input format (*.coveragexml)
  • #​582: Removed method coverage usage for line coverage if no coverage is available
  • #​589: Improved highlighting of hovered table rows in summary table

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot enabled auto-merge (rebase) February 9, 2023 22:13
@github-actions github-actions bot added this to the v0.19.8 milestone Feb 9, 2023
@renovate renovate bot merged commit dfd0bc1 into master Feb 9, 2023
@renovate renovate bot deleted the renovate/reportgenerator branch February 9, 2023 22:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants