dkackman / LinqStatistics

Linq extensions to calculate basic statistics
https://dkackman.github.io/LinqStatistics/
Apache License 2.0
99 stars 29 forks source link

Bump Microsoft.NetFramework.Analyzers from 3.3.0 to 3.3.2 in /src/LinqStatistics #25

Closed dependabot[bot] closed 3 years ago

dependabot[bot] commented 3 years ago

Bumps Microsoft.NetFramework.Analyzers from 3.3.0 to 3.3.2.

Release notes

Sourced from Microsoft.NetFramework.Analyzers's releases.

v3.3.2

Release build of Roslyn-analyzers based on Microsoft.CodeAnalysis 3.3.0 NuGet packages. Works with VS 2019 16.3 or later.

  • Contains important functionality and performance bug fixes on top of v3.3.1 release
  • New deprecation warning CA9998 for Microsoft.CodeAnalysis.FxCopAnalyzers package: FxCopAnalyzers package has been deprecated in favor of 'Microsoft.CodeAnalysis.NetAnalyzers', that ships with the .NET SDK. Please refer to https://docs.microsoft.com/visualstudio/code-quality/migrate-from-fxcop-analyzers-to-net-analyzers to migrate to .NET analyzers.

v3.3.1

Release build of Roslyn-analyzers based on Microsoft.CodeAnalysis 3.3.0 NuGet packages. Works with VS 2019 16.3 or later.

Contains following important changes on top of v3.3.0 release:

Bug Fixes

  • Functionality and performance bug fixes
  • Tainted data rules improvements
  • CA5377: Don't warn when unable to get the control flow graph for dataflow analysis
  • CA3075: Fix false positive on XmlReader.Create(string) invocations
  • Optimizing error list refresh times for full compilation analyzers in Visual Studio 2019 16.9

Additional analyzers/fixers

Added

  • Globalization
    • CA1310: Specify StringComparison for correctness -- Enabled by default
  • Interoperability
    • CA1416: Validate platform compatibility -- Enabled by default

Changed

  • Globalization
    • CA1307: Specify StringComparison for clarity -- Now disabled by default
Commits
  • 4e0e1e8 Merge pull request #4494 from dotnet/merges/release/5.0.2xx-to-master
  • 5530a8b Merge branch 'master' into merges/release/5.0.2xx-to-master
  • 26b2159 Merge pull request #4492 from mavasani/Issue4491_5_0_2xx
  • 23619eb Harden InterproceduralAnalysisConfiguration to prevent null tree argument
  • 9df0075 Merge pull request #4490 from mavasani/FI_5_0_2xx
  • 5671c0b Merge remote-tracking branch 'upstream/release/5.0.2xx' into FI_5_0_2xx
  • f7aad5c Merge pull request #4489 from dotnet/mavasani-patch-1
  • 389ac2f Update Program.cs
  • 3b7bb4a Merge pull request #4488 from dotnet/netanalyzers-5-0-1
  • 704496d Update auto-generated documentation file by running msbuild /t:pack
  • 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 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)
dependabot[bot] commented 3 years ago

Looks like Microsoft.NetFramework.Analyzers is up-to-date now, so this is no longer needed.