Skip to content

Move CI to *-latest runners and sync vcpkg baseline with runner images - #366

Draft
Bill Avery (wravery) with Copilot wants to merge 1 commit into
mainfrom
copilot/update-github-actions-runners
Draft

Bill Avery (wravery) with Copilot wants to merge 1 commit into
mainfrom
copilot/update-github-actions-runners

Conversation

Copilot AI commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

Ahead of the next release, the workflows were audited for stale runner images, outdated action tags, and a vcpkg baseline that no longer matches what's preinstalled on the hosted runners.

Runner images

  • macOS: macos-13 (Intel, deprecated) → macos-latest (macOS 26, arm64). Cache key updated vcpkg-binaries-x64-osxvcpkg-binaries-arm64-osx to match the new default triplet; the arm64 cache starts cold on first run.
  • Windows: windows-2022windows-latest (Windows Server 2025). That image ships Visual Studio Enterprise 2026 only, so the generator changes and the job is renamed vs2022vs2026:
    -    -G "Visual Studio 17 2022" -A "$msbuildArch"
    +    -G "Visual Studio 18 2026" -A "$msbuildArch"
    x86/x64 MSVC toolsets are still present in the image, so the arch/libs/config matrix is unchanged. CMake on that image is 4.4.3, which knows the VS 18 generator.
  • Linux: already on ubuntu-latest; left as-is.

vcpkg

  • builtin-baseline04a9d8e5212d01ee1dd9478eadd9caade4f8b0d4, the vcpkg commit preinstalled on all three latest images (ubuntu-24.04, macOS 26, Windows Server 2025 all report "build from commit 04a9d8e521"), so VCPKG_INSTALLATION_ROOT and the manifest agree.

Action tags

  • actions/checkout (3d3c42e5… = v7.0.1) and actions/cache (55cc8345… = v6.1.0) are already pinned to the newest releases; unchanged.

Worth watching on this branch: the first Windows build under VS 2026 and the first macOS arm64 build.

Co-authored-by: wravery <6502881+wravery@users.noreply.github.com>
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