Skip to content

Releases: leonardochaia/dotnet-affected

v4.0.1

26 Sep 17:29
cfdb3a6
Compare
Choose a tag to compare

What's Changed

Full Changelog: v4.0.0...v4.0.1

v4.0.0

15 Jan 11:21
6a83d2f
Compare
Choose a tag to compare

This release adds support for net8 and drops support for netcore3.1 since its EOL.
v4 supports net6, net7 and net8.

BREAKING CHANGES:

What's Changed

New Contributors

Full Changelog: v3.2.0...v4.0.0

v3.2.0

12 Jul 11:45
84c86fb
Compare
Choose a tag to compare

Breaking Changes

There shouldn't be any breaking changes.

New Features

  • --exclude argument that can be used to exclude projects using regex

What's Changed

New Contributors

Full Changelog: v3.1.1...v3.2.0

v3.1.1

09 Mar 22:51
5784758
Compare
Choose a tag to compare

Fixes

  • Fixes #75: issue while running on Alpine Linux.

Full Changelog: v3.1.0...v3.1.1

v3.1.0

06 Mar 16:00
1486c15
Compare
Choose a tag to compare

New Features

  • Adds support for .fsproj and .vbproj files
  • Adds json output formatter using System.Text.Json
  • Non-SDK projects should be supported (tests were added)

What's Changed

Full Changelog: v3.0.0...v3.1.0

v3.0.0

02 Mar 11:31
cd71eb1
Compare
Choose a tag to compare

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

This release includes new nuget packages for:

  1. DotnetAffected.Abstractions : includes interfaces / entities for dotnet affected
  2. DotnetAffected.Core: includes the core processing logic for discovering and detecting affected projects
  3. DotnetAffected.Tasks: custom MSBuild Task for executing dotnet-affected using MSBuild without the dotnet-affected CLI

BREAKING CHANGES

  • Project files (like csproj) will be evaluated in order to determine which files would affect the project, which may end up detecting affected files that were not detected previously

What's Changed

New Contributors

Full Changelog: v2.2.0...v3.0.0

v3.0.0-preview-4

02 Jan 13:53
49b0eb9
Compare
Choose a tag to compare
v3.0.0-preview-4 Pre-release
Pre-release

If upgrading from v2, please read dotnet-affected v3 preview-1, preview-2 and preview-3 since there are breaking changes.

What's Changed

New Contributors

Full Changelog: v3.0.0-preview-3...v3.0.0-preview-4

v3.0.0-preview-3

14 Oct 10:12
002cc49
Compare
Choose a tag to compare
v3.0.0-preview-3 Pre-release
Pre-release

If upgrading from v2, please read dotnet-affected v3 preview-1 and preview-2 since there are breaking changes.

What's Changed

New Contributors

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

v3.0.0-preview-2

06 Sep 23:43
9b9aa61
Compare
Choose a tag to compare
v3.0.0-preview-2 Pre-release
Pre-release

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

Read preview-1 release notes as well

What's Changed

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

v3.0.0-preview-1

29 Jul 23:30
86dd9e4
Compare
Choose a tag to compare
v3.0.0-preview-1 Pre-release
Pre-release

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

New Contributors

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