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.
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
lower the baseline version for system.text.encodings.web #49671
lower the baseline version for system.text.encodings.web #49671
Changes from 2 commits
adc7cfb
2b6c9a9
a28f0fc
8934eb9
9fc65d7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious if we want to do this or not.
This would mean that JSON wouldn't bring the security fix made to STEW. What's your thinking @GrabYourPitchforks?
On the plus side, it would mean that ASP.NET doesn't see that new version from STEW (though they might be able to intentionally downgrade). Is it possible to have ASP.NET test with and without the baseline?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't sound right to downgrade the baseline and miss the security fix when STEW is transitively referenced.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We discussed with ASP.NET folks over teams, let's undo the change to the baseline: keep it at 5.0.1 here. They'll make some customizations to their build to avoid consuming the versioned S.T.E.W.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My main concern would be somebody adding a package ref to System.Text.Json, then to S.T.E.W, and as a result missing the fix because I believe NuGet will pull in the existing transitive package reference.