How is the vcpkg version in the runner images determined?

[miriameng]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Actions Runner Image

Discussion Details

Currently seeing "Vcpkg (build from commit b1b19307e2)", how is this determined? Is it possible for the runner images to always pick up the latest vcpkg release?

[GustavoEsser]

The GitHub Actions runner images don’t always use the latest vcpkg release.
Instead, they are built periodically against a fixed commit from the vcpkg repository (e.g., b1b19307e2). This ensures reproducibility and stability across workflows, since using “always latest” could break builds unexpectedly.

If you want to always get the latest version (or a specific release) of vcpkg, you need to install it manually in your workflow, for example:

- name: Install latest vcpkg
  run: |
    git clone https://github.com/microsoft/vcpkg.git
    ./vcpkg/bootstrap-vcpkg.sh

This way you’re not dependent on the runner image update cycle.

[miriameng]

As long as builtin-baseline is used in vcpkg.json, reproducibility and stability should be guaranteed, so the GitHub Actions runner images should be able to have latest vcpkg release and not cause problems.

The issue is with the introduction of dependabot for vcpkg https://devblogs.microsoft.com/cppblog/dependabot-support-for-vcpkg/, once dependabot updates the builtin-baseline to the latest vcpkg release, the default vcpkg in the GitHub Actions runner images won't work, and it would be nice not having to install vcpkg ourselves.

[zephinax]

Hi @GustavoEsser,

Thanks for clarifying! That makes sense — using a fixed commit definitely ensures reproducibility and avoids unexpected build failures.

I’ll go ahead and manually install the latest vcpkg in my workflow as you suggested. Just to confirm, this approach won’t interfere with the preinstalled tools on the runner, right?

[GustavoEsser]

Hello @zephinax

Correct, it won’t interfere with the preinstalled tools.

When you clone and bootstrap vcpkg inside your workflow, it will just live in your job’s workspace. The preinstalled version on the runner stays untouched, so you’ll only be using the one you installed explicitly.

[shaunwilliams821-maker]

The vcpkg version in the runner images is typically pinned to a specific commit maintained by the GitHub Actions/runner-images team. They periodically update it based on stability testing and compatibility with the most widely used packages.
If you need a specific version, you can always override the pre-installed one by adding a step in your workflow:

• name: Install specific vcpkg version
  run: |
  git clone https://github.com/microsoft/vcpkg.git
  cd vcpkg
  git checkout <commit_or_tag>
  ./bootstrap-vcpkg.sh
  This way, you’re not dependent on the default version shipped with the runner image.

[miriameng]

As long as builtin-baseline is used in vcpkg.json, reproducibility and stability should be guaranteed, so the GitHub Actions runner images should be able to have latest vcpkg release and not cause problems.

The issue is with the introduction of dependabot for vcpkg https://devblogs.microsoft.com/cppblog/dependabot-support-for-vcpkg/, once dependabot updates the builtin-baseline to the latest vcpkg release, the default vcpkg in the GitHub Actions runner images won't work, and it would be nice not having to install vcpkg ourselves.

[erik-bershel]

Hey @miriameng! 👋

I am from Runner Images team. There is such a moment here. When assembling an image, we always use the latest available version of the package. This is achieved in the following way: each time the installation occurs from the current state of the repository. For example, here is a simple installer script that we use for Ubuntu: https://github.com/actions/runner-images/blob/main/images/ubuntu/scripts/build/install-vcpkg.sh

But due to our release cycle (the planned release of updates is weekly), there is always a possibility that by the time of launch the repository has already been updated. Let's consider in more detail: we built the image on Monday, the deployment was completed on Thursday, your task was completed on Saturday, and at this time vcpkg released a change, for example, on Wednesday.

Unfortunately, we cannot update the version on the fly, since the image is a fairly monolithic structure. Because of this, we recommend that if necessary, using a guaranteed latest version, you update the package yourself in runtime.

[miriameng]

Thanks a lot for the explanation. The main motivation of wanting a up to date vcpkg is because of the introduction of dependabot for vcpkg https://devblogs.microsoft.com/cppblog/dependabot-support-for-vcpkg/, once dependabot updates the builtin-baseline to the latest vcpkg release, there's a possibility that the default vcpkg in the runner images won't work, and it would be nice to not having to install vcpkg ourselves. Wish that somehow the runner images team, vcpkg team, and dependabot team can be more coordinated to enable this.

[King-luiz]

The vcpkg version on GitHub-hosted runner images isn't 'live' — it's pinned at the time the runner image is built.

• Each Actions runner image (e.g., ubuntu-22.04) is built from the actions/runner-images repository.

• During that build process, vcpkg is cloned at a specific commit (you'll see a line like 'Vcpkg (build from commit b1b19307e2)' in the build logs).

• That means the version you see is determined by whatever commit of vcpkg was current when the image was generated. Runner images are refreshed roughly weekly, so vcpkg won't necessarily be at the absolute latest commit.

If you need the very latest vcpkg version in your workflow:

1. Add a step to update it manually, for example:
   '''yaml
   • name: Update vcpkg
     run: git -C "${VCPKG_INSTALLATION_ROOT}" pull

[rubel120]

Easy Steps to Manage vcpkg Version in GitHub Actions

1. Use the vcpkg version preinstalled in the runner image:

This is pinned to a commit fixed at the time the image was built.

Suitable for stable and reproducible builds.

2. To get the latest or specific vcpkg version manually:

Add a step in your workflow to clone the vcpkg repository.

Bootstrap vcpkg as needed.

This approach won't interfere with preinstalled tools on the runner.

Example workflow snippet to install latest vcpkg manually:

• name: Install latest vcpkg
  run: |
  git clone https://github.com/microsoft/vcpkg.git
  ./vcpkg/bootstrap-vcpkg.sh

This manual installation ensures you are always using the latest or a chosen commit of vcpkg independently of the runner image update cycle.

This method is commonly recommended especially when you want to keep up with new releases or avoid issues arising from mismatched versions, like those caused by Dependabot updates to the vcpkg baseline.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬