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.12 #855

Merged
merged 1 commit into from
Nov 20, 2022
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 16, 2022

Mend Renovate

This PR contains the following updates:

Package Type Update Change
ReportGenerator nuget patch 5.1.6 -> 5.1.12
dotnet-reportgenerator-globaltool nuget patch 5.1.6 -> 5.1.12

Release Notes

danielpalme/ReportGenerator

v5.1.12: ReportGenerator_5.1.12

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

Changes:
  • #​548: Improved handling of OverflowException

v5.1.11: ReportGenerator_5.1.11

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

Changes:

  • #​556: Generate text reports without UTF-8 BOM
  • #​557: Added support for .NET 7

v5.1.10: ReportGenerator_5.1.10

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

Changes:

  • #​534: Added report types: TextDeltaSummary, MarkdownDeltaSummary
  • #​536: Improved support for coverage files generated by CPPCoverage

v5.1.9: ReportGenerator_5.1.9

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

v5.1.8: ReportGenerator_5.1.8

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

v5.1.7: ReportGenerator_5.1.7

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

Changes:

  • #​516: Improved class name for gcov parser
  • #​516: Added setting for custom assembly name
  • #​517: Riskhotspot filter is now case insensitive

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) May 16, 2022 04:52
@github-actions github-actions bot added this to the v0.19.6 milestone May 16, 2022
@renovate renovate bot changed the title Update reportgenerator to v5.1.7 Update reportgenerator to v5.1.8 May 17, 2022
@renovate renovate bot force-pushed the renovate/reportgenerator branch 2 times, most recently from ed7c5f4 to 867f8ea Compare May 18, 2022 21:36
@renovate renovate bot changed the title Update reportgenerator to v5.1.8 Update reportgenerator to v5.1.9 May 18, 2022
@renovate renovate bot force-pushed the renovate/reportgenerator branch from 867f8ea to 60b1a76 Compare May 21, 2022 00:42
@renovate renovate bot changed the title Update reportgenerator to v5.1.9 Update dependency ReportGenerator to v5.1.9 Jul 18, 2022
@renovate renovate bot changed the title Update dependency ReportGenerator to v5.1.9 Update reportgenerator to v5.1.9 Jul 18, 2022
@renovate renovate bot changed the title Update reportgenerator to v5.1.9 Update reportgenerator to v5.1.10 Sep 25, 2022
@renovate renovate bot changed the title Update reportgenerator to v5.1.10 Update reportgenerator to v5.1.12 Nov 20, 2022
@renovate renovate bot force-pushed the renovate/reportgenerator branch 2 times, most recently from cee0e2f to 2ac81ef Compare November 20, 2022 14:53
@github-actions github-actions bot modified the milestones: v0.19.6, v0.19.7 Nov 20, 2022
@renovate renovate bot merged commit e88cb17 into master Nov 20, 2022
@renovate renovate bot deleted the renovate/reportgenerator branch November 20, 2022 15:59
@github-actions github-actions bot added the mysterious We forgot to label this label Nov 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mysterious We forgot to label this
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants