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

[0.74] Bump minimum VS version to 17.11.0 #13583

Merged
merged 2 commits into from
Aug 16, 2024

Conversation

jonthysell
Copy link
Contributor

@jonthysell jonthysell commented Aug 16, 2024

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

Microsoft Reviewers: Open in CodeFlow

@jonthysell jonthysell requested review from a team as code owners August 16, 2024 17:52
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
@jonthysell jonthysell merged commit 468cc10 into microsoft:0.74-stable Aug 16, 2024
95 checks passed
@jonthysell jonthysell deleted the vs11_74 branch August 20, 2024 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants