Bump protocolbuffers/csharp@28.3 to netstandard2.0
#1592
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
.NET 9 SDK raises a (suppressable) build warning about this, largely to encourage developers to upgrade. This should not be an issue for consumers, as the more important consideration is the hosting application's target framework. More importantly, using `netstandard1.1` results in a vulnerable version of `System.Net.Http` being pulled in (`4.3.0`) via `Google.Protobuf`'s `netstandard1.1` deps. Upgrading to `netstandard2.0` resolves this. `grpc/csharp` is already using `netstandard2.0`. No other C# plugins exist.
stefanvanburen
approved these changes
Nov 14, 2024
Member
stefanvanburen
left a comment
stefanvanburen
left a comment
There was a problem hiding this comment.
makes sense to me - would be good to get a confirm from @pkwarren though
pkwarren
approved these changes
Nov 14, 2024
smaye81
pushed a commit
that referenced
this pull request
Nov 26, 2024
.NET 9 SDK [raises](https://learn.microsoft.com/en-ca/dotnet/core/compatibility/sdk/9.0/netstandard-warning) a (suppressable) build warning about this, largely to encourage developers to upgrade. This should not be an issue for consumers, as the more important consideration is the hosting application's target framework. More importantly, using `netstandard1.1` results in a vulnerable version of `System.Net.Http` being pulled in (`4.3.0`) via `Google.Protobuf`'s `netstandard1.1` deps. Upgrading to `netstandard2.0` resolves this. `grpc/csharp` is already using `netstandard2.0`. No other C# plugins exist.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
.NET 9 SDK raises a (suppressable) build warning about this, largely to encourage developers to upgrade. This should not be an issue for consumers, as the more important consideration is the hosting application's target framework.
More importantly, using
netstandard1.1results in a vulnerable version ofSystem.Net.Httpbeing pulled in (4.3.0) viaGoogle.Protobuf'snetstandard1.1deps. Upgrading tonetstandard2.0resolves this.grpc/csharpis already usingnetstandard2.0. No other C# plugins exist.