Releases: dailydevops/analyzer
Releases · dailydevops/analyzer
Release list
0.15.0
0.14.9
0.14.8
0.14.7
What's Changed
- fix(NE0010): propagate CancellationToken as a named argument (#47) @samtrion
- fix(usage): NE0009 recognize a leading cancellation check inside loops (#45) @samtrion
- fix(NE0008): recognize common BCL value type names (#46) @samtrion
- chore(deps): update dependency netevolve.defaults to 2.8.0 (#44) @renovate[bot], @samtrion
0.14.2
0.14.1
What's Changed
- chore(release): move NE0001-NE0011 into AnalyzerReleases.Shipped.md (#42) @samtrion
- feat(usage): NE0010 require a CancellationToken parameter on Task/ValueTask/IAsyncEnumerable-returning methods (#39) @samtrion
- feat(style): NE0011 avoid #region directives, warn when nested in a member body (#40) @samtrion
- feat(usage): NE0009 require a cancellation check when a method has a CancellationToken parameter (#41) @samtrion
- feat(documentation): NE0008 use cref for native type names in doc comments (#38) @samtrion
- feat(documentation): suppress MA0154 wherever NE0007 already reports it (#37) @samtrion
- refactor(documentation): exclude native type names from the recognized keyword set (#36) @samtrion
- docs: simplify the Roslyn-variant PropertyGroup label comment (#35) @samtrion
- docs: replace literal three dots with an ellipsis character in prose (#34) @samtrion
- feat(documentation): NE0007 also flag
elements for langword keywords (#33) @samtrion
0.9.0
What's Changed
- feat(documentation): NE0007 use langword instead of for C# keywords (#32) @samtrion
- chore(deps): update dependency microsoft.codeanalysis.csharp.workspaces to v5 (#2) @renovate[bot]
- chore(deps): update dependency microsoft.codeanalysis.csharp to v5 (#1) @renovate[bot]
- feat: build the analyzer against four Roslyn API versions (#30) @samtrion
0.7.1
0.7.0
What's Changed
- No changes
Warning
Release Drafter could not find a previous published release for dailydevops/analyzer. This draft was created without a comparison baseline.
Important
Treat this draft as a manual starting point.
Review the proposed version, tag, and notes before publishing.
If you did not expect this to happen, open an issue.