DotNetAnalyzers / AspNetCoreAnalyzers

MIT License
62 stars 4 forks source link

Bump Microsoft.CodeAnalysis.CSharp.Workspaces from 4.5.0 to 4.7.0 #176

Open dependabot[bot] opened 11 months ago

dependabot[bot] commented 11 months ago

Bumps Microsoft.CodeAnalysis.CSharp.Workspaces from 4.5.0 to 4.7.0.

Release notes

Sourced from Microsoft.CodeAnalysis.CSharp.Workspaces's releases.

.NET 6.0.1

Release

.NET 5.0.4

Release

.NET 5.0.2

Release Notes Install Instructions

Repos

Changelog

Sourced from Microsoft.CodeAnalysis.CSharp.Workspaces's changelog.

Version 4.5.0

SymbolDisplayFormat.CSharpErrorMessageFormat and CSharpShortErrorMessageFormat now include parameter names by default if used on a standalone IParameterSymbol. For example, parameter p in void M(ref int p) was previously formatted as "ref int" and now it is formatted as "ref int p".

Version 4.7.0

SymbolDisplayFormat includes parameter name when invoked on IParameterSymbol

All SymbolDisplayFormats (predefined and user-created) now include parameter names by default if used on a standalone IParameterSymbol for consistency with predefined formats (see the breaking change for version 4.5.0 above).

Changed IncrementalStepRunReason when a modified input produced a new output

IncrementalGeneratorRunStep.Outputs previously contained IncrementalStepRunReason.Modified as Reason when the input to the step was modified in a way that produced a new output. Now the reason will be reported more accurately as IncrementalStepRunReason.New.

Version 4.8.0

Changed Assembly.Location behavior in non-Windows

The value of Assembly.Location previously held the location on disk where an analyzer or source generator was loaded from. This could be either the original location or the shadow copy location. In 4.8 this will be "" in certain cases when running on non Windows platforms. This is due the compiler server loading assemblies using AssemblyLoadContext.LoadFromStream instead of loading from disk.

This could already happen in other load scenarios but this change moves it into mainline build scenarios.

Commits


Dependabot compatibility score

You can trigger a rebase of this PR 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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.