-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[release/9.0-staging] Bump System.Text.Json toolset version #113385
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
[release/9.0-staging] Bump System.Text.Json toolset version #113385
Conversation
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
Do any of the tasks that use this ship in the product - and if so - can we guarantee that every VS version that supports 9.0 will have this update to MSBuild? |
@akoeplinger indicated VS 17.4 has the 9 bump. Is that the min VS version for 9? |
@steveisok Friendly reminder that code complete is on April 14th for the May Release. If you'd like to get this change included in that release, please get a Tactics approval (if product change) and merge this PR before that date. |
@steveisok friendly reminder that code complete is on Monday May 12th (2:00 PM Pacific) for the June Release. If you'd like to get this change included in that release, please get a Tactics approval and merge this PR before the deadline. |
@steveisok reminder that servicing code complete for 9.0.7 is today @ 3PM PST. |
@steveisok are you planning to have this in this servicing release? if so, please get this approved and merged soon. Just reminder Code-complete is 14-Jul 4pm PT cut-off |
@dotnet/runtime-infrastructure can one or more of you give this another review / sign-off? |
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.
LGTM
/ba-g timeouts |
Backport of #113384 to release/9.0-staging
/cc @steveisok
Customer Impact
[Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.]
Regression
[If yes, specify when the regression was introduced. Provide the PR or commit if known.]
Testing
[How was the fix verified? How was the issue missed previously? What tests were added?]
Risk
[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]
IMPORTANT: If this backport is for a servicing release, please verify that:
release/X.0-staging
, notrelease/X.0
.Package authoring no longer needed in .NET 9
IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.