diff options
| author | 5an7y-Microsoft <[email protected]> | 2026-05-06 10:43:24 -0700 |
|---|---|---|
| committer | GitHub <[email protected]> | 2026-05-06 10:43:24 -0700 |
| commit | 63a98a6d0eced10f85b9192bbf92d711af0715fc (patch) | |
| tree | f1dba30aa1f1a890c56ca53db1092c88546af12d /.github | |
| parent | ae2b6c4da5c92669afeb8e260c6377958437f1bd (diff) | |
Change GitHub Actions runner to windows-2025-vs2026user/jvalesmena/wdk2604
Updated the runner configuration for GitHub Actions to use 'windows-2025-vs2026' with Visual Studio 2026.
Diffstat (limited to '.github')
| -rw-r--r-- | .github/Build-with-GitHub.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/.github/Build-with-GitHub.md b/.github/Build-with-GitHub.md index c4a10962..cd1715ba 100644 --- a/.github/Build-with-GitHub.md +++ b/.github/Build-with-GitHub.md @@ -2,7 +2,7 @@ If you use GitHub to host your code, you can leverage [GitHub Actions](https://docs.github.com/en/actions) to create automated workflows to build your driver projects. -`windows-2022` runner (provided by `windows-latest`) is configured with Windows Driver Kit version 22H2 and Visual Studio 2022 off the box, so most solutions can be built by running `msbuild` directly. +`windows-2025-vs2026` runner is configured with Visual Studio 2026 off the box, so most solutions can be built by running `msbuild` directly using the WDK NuGet package. ```yaml name: Build driver solution @@ -16,7 +16,7 @@ jobs: matrix: configuration: [Debug, Release] platform: [x64] - runs-on: windows-2022 + runs-on: windows-2025-vs2026 env: Solution_Path: path\to\driver\solution.sln steps: |