v3.0.0-preview-2

This release includes nuget packages for DotnetAffected.Core and DotnetAffected.Abstractions

Read preview-1 release notes as well

What's Changed

• ci: snupkg by @leonardochaia in #53
• refactor: split cli into reusable package by @leonardochaia in #52

Full Changelog: v3.0.0-preview-1...v3.0.0-preview-2

v3.0.0-preview-1

dotnet-affected v3 uses MSBuild.Prediction in order to determine which files belong to which projects. This improves detection of indirectly referenced files like Directory.Build.props and .targets as well as other stuff like signing keys, or files that are excluded from compilation, etc.

Basically the csproj will be evaluated to determine which files belong to each project and find out which projects have changed in order to find their referencing projects

BREAKING CHANGES

• Project files (like csproj) will be evaluated in order to determine which files would affect the project

What's Changed

• ci: fixes windows builds by @leonardochaia in #43
• Add cache to store repeated dependency tree calcs by @megakid in #39
• refactor: make tests deterministic by @leonardochaia in #44
• refactor: tests to use shared testing infrastructure by @leonardochaia in #45
• Adds benchmarks using DotnetBenchmark by @leonardochaia in #47
• refactor: use referencing projects by @leonardochaia in #49
• chore: micro & macrobenchmarks by @leonardochaia in #50
• refactor: use Microsoft.Build.Predictions by @leonardochaia in #46

New Contributors

• @megakid made their first contribution in #39

Full Changelog: v2.2.0...v3.0.0-preview-1

v2.2.0

REMARKS: When using net6, v6.0.2 or greater is required

Breaking Changes

Stdout output has changed. If you were piping dotnet-affected's stdout, I recommend using the --format text option to get a text representation of changed projects. (If you need another format just create an issue)

What's Changed

• chore: fixes tests on windows by @leonardochaia in #29
• More verbose by @satano in #28
• refactor: tests to use repository by @leonardochaia in #30
• refactor: split up context by @leonardochaia in #32
• Adds support for detecting affected projects for version changes in centrally managed NuGet packages by @wterpstra in #23
• chore: updates packages to latest versions by @leonardochaia in #33
• feat: support packages with conditions by @leonardochaia in #34
• Fixes NullReference exception when Directory.Packages.props is added or FileNotFoundException when removed by @wterpstra in #37

Full Changelog: v2.1.0...v2.2.0

v2.2.0-preview

REMARKS: When using net6, v6.0.2 or greater is required

Breaking Changes

Stdout output has changed. If you were piping dotnet-affected's stdout, I recommend using the --format text option to get a text representation of changed projects. (If you need another format just create an issue)

What's Changed

• chore: fixes tests on windows by @leonardochaia in #29
• More verbose by @satano in #28
• refactor: tests to use repository by @leonardochaia in #30
• refactor: split up context by @leonardochaia in #32
• Adds support for detecting affected projects for version changes in centrally managed NuGet packages by @wterpstra in #23
• chore: updates packages to latest versions by @leonardochaia in #33
• feat: support packages with conditions by @leonardochaia in #34

Full Changelog: v2.1.0...v2.2.0-preview

v2.1.0

This is the first stable release for dotnet-affected

Single new feature has been introduced, support for .NET 6.

Currently, netcore3.1, net5 and net6 are supported.

REMARKS: When using net6, net 6.0.2 is required

v2.0.0-preview-1

BREAKING CHANGES

1. dotnet affected generate has been deprecated in favor of dotnet affected
2. When using --verbose flag, changed/affected projects are not displayed anymore. Can be obtained using describe command.

New Features:

1. Output Formatters: add --format text traversal to obtain both: a .txt and .proj file of affected and changed projects

v1.0.0-preview-5

Fix:

1. Repository path not being inferred correctly when using default values. commit

This is most likely the final v1.0.0 version.

v1.0.0-preview-4

Internal refactors.
No known issues.
No new features.

Breaking changes:

1. Exit code 166 will be returned when there are no changed projects. Despite of whether there are projects affected by those changes or not.

v1.0.0-preview-3

Fixes:

1. Running in Azure Pipelines throws exception #6

v1.0.0-preview-2

BREAKING CHANGES:

1. dotnet affected will return exit code 130 when there are no affected projects, instead of the previous version which returned 0. #1

Features:

1. Adds --solution-path argument, to filter projects by a solution instead of auto-discovering all projects in --repository-path #4

Known Issues:

1. dotnet-affected might not work on Azure DevOps Pipelines. #6