-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 minimum VS version to 17.11.0 #13455
Conversation
Note: This won't pass until the VM image refresh completes, but that will be a good test that the PR fails when it detects the current VM image doesn't have the right VS version. |
Tried to bump us to 17.10.4, but it looks like it breaks our native unit tests: https://developercommunity.visualstudio.com/t/VS2022-17101-throws-an-error-in-Azure-/10678969 So end users should be unblocked by 17.10.4, but we can't update the repo until maybe 17.10.5. |
Tried to bump to 10.17.5, but now DeployAppRecipe is broken again. |
Updating this PR to require the just released 17.11.0. Waiting for the test image to refresh so I can validate everything's clear, then I'll update the main image. |
This reverts commit a56d2a0.
This PR backports microsoft#13455 to 0.75. ## Description This PR bumps the minimum version of VS that RNW expects to 17.11.0. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why To make sure users don't use the regressed builds of VS 2022. Resolves microsoft#13339 Resolves microsoft#13374 ### What Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. ## Screenshots N/A ## Testing `run-windows` now works with 17.11.0. ## Changelog Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
This PR backports microsoft#13455 to 0.74. This PR bumps the minimum version of VS that RNW expects to 17.11.0. - Bug fix (non-breaking change which fixes an issue) To make sure users don't use the regressed builds of VS 2022. Resolves microsoft#13339 Resolves microsoft#13374 Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. N/A `run-windows` now works with 17.11.0. Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
This PR backports microsoft#13455 to 0.74. This PR bumps the minimum version of VS that RNW expects to 17.11.0. - Bug fix (non-breaking change which fixes an issue) To make sure users don't use the regressed builds of VS 2022. Resolves microsoft#13339 Resolves microsoft#13374 Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. N/A `run-windows` now works with 17.11.0. Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
This PR backports microsoft#13455 to 0.73. ## Description This PR bumps the minimum version of VS that RNW expects to 17.11.0. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why To make sure users don't use the regressed builds of VS 2022. Resolves microsoft#13339 Resolves microsoft#13374 ### What Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. ## Screenshots N/A ## Testing `run-windows` now works with 17.11.0. ## Changelog Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
This PR backports microsoft#13455 to 0.72. ## Description This PR bumps the minimum version of VS that RNW expects to 17.11.0. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why To make sure users don't use the regressed builds of VS 2022. Resolves microsoft#13339 Resolves microsoft#13374 ### What Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. ## Screenshots N/A ## Testing `run-windows` now works with 17.11.0. ## Changelog Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
This PR backports #13455 to 0.75. ## Description This PR bumps the minimum version of VS that RNW expects to 17.11.0. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why To make sure users don't use the regressed builds of VS 2022. Resolves #13339 Resolves #13374 ### What Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. ## Screenshots N/A ## Testing `run-windows` now works with 17.11.0. ## Changelog Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
This PR backports #13455 to 0.73. ## Description This PR bumps the minimum version of VS that RNW expects to 17.11.0. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why To make sure users don't use the regressed builds of VS 2022. Resolves #13339 Resolves #13374 ### What Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. ## Screenshots N/A ## Testing `run-windows` now works with 17.11.0. ## Changelog Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
This PR backports #13455 to 0.74. ## Description This PR bumps the minimum version of VS that RNW expects to 17.11.0. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why To make sure users don't use the regressed builds of VS 2022. Resolves #13339 Resolves #13374 ### What Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. ## Screenshots N/A ## Testing `run-windows` now works with 17.11.0. ## Changelog Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
This PR backports #13455 to 0.72. ## Description This PR bumps the minimum version of VS that RNW expects to 17.11.0. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why To make sure users don't use the regressed builds of VS 2022. Resolves #13339 Resolves #13374 ### What Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. ## Screenshots N/A ## Testing `run-windows` now works with 17.11.0. ## Changelog Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
Description
This PR bumps the minimum version of VS that RNW expects to 17.11.0.
Type of Change
Why
To make sure users don't use the regressed builds of VS 2022.
Resolves #13339
Resolves #13374
What
Bumped VS version checks for
run-windows
andrnw-dependencies.ps1
. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4.Screenshots
N/A
Testing
run-windows
now works with 17.11.0.Changelog
Should this change be included in the release notes: yes
Require Visual Studio 2022 >= v17.11.0
Microsoft Reviewers: Open in CodeFlow