CI: restore generated SLN or SLNX on VS 2026 runners - #118
Merged
vdwtanner merged 1 commit intoSep 4, 2026
Conversation
vdwtanner
force-pushed
the
user/tvandewalle/fix-github-actions-slnx-restore
branch
from
September 4, 2026 20:41
dae1e48 to
03220c3
Compare
Jesse Natalie (jenatali)
approved these changes
Sep 4, 2026
vdwtanner
deleted the
user/tvandewalle/fix-github-actions-slnx-restore
branch
September 4, 2026 21:27
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
windows-latestnow resolves to the Windows Server 2025 / Visual Studio 2026 runner. CMake therefore selects the Visual Studio 18 2026 generator, which emits a.slnxsolution. The workflow hard-codes a generated.slnpath, so NuGet restore fails withInput file does not existimmediately after successful CMake generation.This is independent of the open Dependabot action-update PR: a separate run using the previous
actions/checkoutandNuGet/setup-nugetversions fails identically.Fix
Discover the single generated
.slnor.slnxfile and restore that path. The check fails loudly if CMake generates zero or multiple solutions. Explicitnuget.exe restoreis retained for nativepackages.configcompatibility.Validation
windows-2025, Visual Studio 17 2022,.sln) with the current failure (windows-2025-vs2026, Visual Studio 18 2026, missing hard-coded.sln).git diff --checkpasses; this PR changes only.github/workflows/prBuild.yml..slnxpath.