Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump Microsoft.CodeAnalysis.CSharp.Workspaces, Microsoft.CodeAnalysis.Common, Microsoft.CodeAnalysis.Analyzers and Microsoft.CodeAnalysis.CSharp #57

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Feb 22, 2024

Bumps Microsoft.CodeAnalysis.CSharp.Workspaces, Microsoft.CodeAnalysis.Common, Microsoft.CodeAnalysis.Analyzers and Microsoft.CodeAnalysis.CSharp. These dependencies needed to be updated together.
Updates Microsoft.CodeAnalysis.CSharp.Workspaces from 3.9.0 to 4.8.0

Release notes

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

.NET 7.0 Preview 5

Release

.NET 7.0 Preview 2

Release

.NET 7.0 Preview 1

Release

.NET 6.0.1

Release

.NET 6.0

Release

.NET 6.0 Preview 6

Release

.NET 6.0 Preview 4

Release

.NET 6.0 Preview 5

Release

.NET 6.0 Preview 3

Release

.NET 6.0 Preview 2

Release

.NET 6.0 Preview 1

Release

Changelog

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

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.

Deprecation warning for SyntaxNode serialization

The ability to serialize/deserialize a SyntaxNode to/from a Stream has been deprecated. The code for this still exists in Roslyn, but attempting to call the APIs to perform these functions will result in 'Obsolete' warnings being reported. A future version of Roslyn will remove this functionality entirely. This functionality could only work for a host that wrote out the nodes to a stream, and later read it back in within the same process instance. It could not be used to communicate across processes, or for persisting nodes to disk to be read in at a later time by a new host sessions. This functionality originally existed for the days when Roslyn was hosted in 32bit processes with limited address space. That is no longer a mainline supported scenario. Clients can get similar functionality by persisting the text of the node, and parsing it back out when needed.

PR: dotnet/roslyn#70365

Version 4.9.0

Obsoletion and removal of SyntaxNode serialization.

Continuation of the deprecation that happened in 4.8.0 (see information above). In 4.9.0 this functionality is now entirely removed, and will issue both an obsoletion error, and will throw at runtime if the APIs are used.

PR: dotnet/roslyn#70277

Changes in Microsoft.CodeAnalysis.Emit.EmitBaseline.CreateInitialBaseline method

A new required parameter Compilation has been added. Existing overloads without this parameter no longer work and throw NotSupportedException.

Changes in Microsoft.CodeAnalysis.Emit.SemanticEdit constructors

The value of preserveLocalVariables passed to the constructors is no longer used.

Commits

Updates Microsoft.CodeAnalysis.Common from 3.9.0 to 4.8.0

Release notes

Sourced from Microsoft.CodeAnalysis.Common's releases.

.NET 7.0 Preview 5

Release

.NET 7.0 Preview 2

Release

.NET 7.0 Preview 1

Release

.NET 6.0.1

Release

.NET 6.0

Release

.NET 6.0 Preview 6

Release

.NET 6.0 Preview 4

Release

.NET 6.0 Preview 5

Release

.NET 6.0 Preview 3

Release

.NET 6.0 Preview 2

Release

.NET 6.0 Preview 1

Release

Changelog

Sourced from Microsoft.CodeAnalysis.Common's changelog.

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.

Deprecation warning for SyntaxNode serialization

The ability to serialize/deserialize a SyntaxNode to/from a Stream has been deprecated. The code for this still exists in Roslyn, but attempting to call the APIs to perform these functions will result in 'Obsolete' warnings being reported. A future version of Roslyn will remove this functionality entirely. This functionality could only work for a host that wrote out the nodes to a stream, and later read it back in within the same process instance. It could not be used to communicate across processes, or for persisting nodes to disk to be read in at a later time by a new host sessions. This functionality originally existed for the days when Roslyn was hosted in 32bit processes with limited address space. That is no longer a mainline supported scenario. Clients can get similar functionality by persisting the text of the node, and parsing it back out when needed.

PR: dotnet/roslyn#70365

Version 4.9.0

Obsoletion and removal of SyntaxNode serialization.

Continuation of the deprecation that happened in 4.8.0 (see information above). In 4.9.0 this functionality is now entirely removed, and will issue both an obsoletion error, and will throw at runtime if the APIs are used.

PR: dotnet/roslyn#70277

Changes in Microsoft.CodeAnalysis.Emit.EmitBaseline.CreateInitialBaseline method

A new required parameter Compilation has been added. Existing overloads without this parameter no longer work and throw NotSupportedException.

Changes in Microsoft.CodeAnalysis.Emit.SemanticEdit constructors

The value of preserveLocalVariables passed to the constructors is no longer used.

Commits

Updates Microsoft.CodeAnalysis.Analyzers from 3.0.0 to 3.3.4

Release notes

Sourced from Microsoft.CodeAnalysis.Analyzers's releases.

v3.3.4

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

  • Contains important functionality and performance bug fixes on top of v3.3.3 release

v3.3.3

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

  • Contains important functionality and performance bug fixes on top of v3.3.2 release

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

v3.3.0

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.0.0 release

The new security rules CA2350-CA2362 can help find vulnerabilities related to DataSet and DataTable security guidance.

Feature

Editorconfig based file/directory level options configuration. See details here

... (truncated)

Commits
  • 22ea642 Merge pull request #6436 from ViktorHofer/patch-1
  • 9018071 Fix buildtransitive vs buildTransitive difference
  • afa5665 [main] Update dependencies from dotnet/arcade (#6423)
  • afee469 Merge pull request #6427 from mavasani/CodeAnalysisTreatWarningsAsErrors_Glob...
  • b858999 Merge pull request #6430 from dotnet/locfiles/be3abf9f-1f22-469b-b26d-7648587...
  • 0cbc3c5 Localized file check-in by OneLocBuild Task: Build definition ID 830: Build I...
  • 113dadc Merge pull request #6429 from dotnet/revert-6364-net7-tests
  • 356147f Revert "Move tests to target .NET 7"
  • 1d7244a Update documentation for CodeAnalysisTreatWarningsAsErrors implementation
  • 6c028d3 Re-implement CodeAnalysisTreatWarningsAsErrors with globalconfig files
  • Additional commits viewable in compare view

Updates Microsoft.CodeAnalysis.CSharp from 3.9.0 to 4.8.0

Release notes

Sourced from Microsoft.CodeAnalysis.CSharp's releases.

.NET 7.0 Preview 5

Release

.NET 7.0 Preview 2

Release

.NET 7.0 Preview 1

Release

.NET 6.0.1

Release

.NET 6.0

Release

.NET 6.0 Preview 6

Release

.NET 6.0 Preview 4

Release

.NET 6.0 Preview 5

Release

.NET 6.0 Preview 3

Release

.NET 6.0 Preview 2

Release

.NET 6.0 Preview 1

Release

Changelog

Sourced from Microsoft.CodeAnalysis.CSharp's changelog.

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.

Deprecation warning for SyntaxNode serialization

The ability to serialize/deserialize a SyntaxNode to/from a Stream has been deprecated. The code for this still exists in Roslyn, but attempting to call the APIs to perform these functions will result in 'Obsolete' warnings being reported. A future version of Roslyn will remove this functionality entirely. This functionality could only work for a host that wrote out the nodes to a stream, and later read it back in within the same process instance. It could not be used to communicate across processes, or for persisting nodes to disk to be read in at a later time by a new host sessions. This functionality originally existed for the days when Roslyn was hosted in 32bit processes with limited address space. That is no longer a mainline supported scenario. Clients can get similar functionality by persisting the text of the node, and parsing it back out when needed.

PR: dotnet/roslyn#70365

Version 4.9.0

Obsoletion and removal of SyntaxNode serialization.

Continuation of the deprecation that happened in 4.8.0 (see information above). In 4.9.0 this functionality is now entirely removed, and will issue both an obsoletion error, and will throw at runtime if the APIs are used.

PR: dotnet/roslyn#70277

Changes in Microsoft.CodeAnalysis.Emit.EmitBaseline.CreateInitialBaseline method

A new required parameter Compilation has been added. Existing overloads without this parameter no longer work and throw NotSupportedException.

Changes in Microsoft.CodeAnalysis.Emit.SemanticEdit constructors

The value of preserveLocalVariables passed to the constructors is no longer used.

Commits

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 show <dependency name> 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)

….Common, Microsoft.CodeAnalysis.Analyzers and Microsoft.CodeAnalysis.CSharp

Bumps [Microsoft.CodeAnalysis.CSharp.Workspaces](https://github.com/dotnet/roslyn), [Microsoft.CodeAnalysis.Common](https://github.com/dotnet/roslyn), [Microsoft.CodeAnalysis.Analyzers](https://github.com/dotnet/roslyn-analyzers) and [Microsoft.CodeAnalysis.CSharp](https://github.com/dotnet/roslyn). These dependencies needed to be updated together.

Updates `Microsoft.CodeAnalysis.CSharp.Workspaces` from 3.9.0 to 4.8.0
- [Release notes](https://github.com/dotnet/roslyn/releases)
- [Changelog](https://github.com/dotnet/roslyn/blob/main/docs/Breaking%20API%20Changes.md)
- [Commits](https://github.com/dotnet/roslyn/commits)

Updates `Microsoft.CodeAnalysis.Common` from 3.9.0 to 4.8.0
- [Release notes](https://github.com/dotnet/roslyn/releases)
- [Changelog](https://github.com/dotnet/roslyn/blob/main/docs/Breaking%20API%20Changes.md)
- [Commits](https://github.com/dotnet/roslyn/commits)

Updates `Microsoft.CodeAnalysis.Analyzers` from 3.0.0 to 3.3.4
- [Release notes](https://github.com/dotnet/roslyn-analyzers/releases)
- [Changelog](https://github.com/dotnet/roslyn-analyzers/blob/main/PostReleaseActivities.md)
- [Commits](dotnet/roslyn-analyzers@v3.0.0...v3.3.4)

Updates `Microsoft.CodeAnalysis.CSharp` from 3.9.0 to 4.8.0
- [Release notes](https://github.com/dotnet/roslyn/releases)
- [Changelog](https://github.com/dotnet/roslyn/blob/main/docs/Breaking%20API%20Changes.md)
- [Commits](https://github.com/dotnet/roslyn/commits)

---
updated-dependencies:
- dependency-name: Microsoft.CodeAnalysis.CSharp.Workspaces
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: Microsoft.CodeAnalysis.Common
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: Microsoft.CodeAnalysis.Analyzers
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: Microsoft.CodeAnalysis.CSharp
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Copy link
Author

dependabot bot commented on behalf of github Mar 21, 2024

Superseded by #66.

@dependabot dependabot bot closed this Mar 21, 2024
@dependabot dependabot bot deleted the dependabot/nuget/Microsoft.CodeAnalysis.CSharp.Workspaces-and-Microsoft.CodeAnalysis.Common-and-Microsoft.CodeAnalysis.Analyzers-and-Microsoft.CodeAnalysis.CSharp-4.8.0 branch March 21, 2024 00:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants