This blog post summarizes changes to the vcpkg package manager as part of the 2025.06.13 registry release, 2025-04-16, 2025-05-19, and 2025-06-02 tool releases, as well as changes to vcpkg documentation throughout May and June. This release includes bug fixes, several documentation changes, and the removal of the x-gha binary caching provider for GitHub (alternatives are described below).

Some stats for this period:

• There are now 2,621 total ports available in the vcpkg curated registry. A port is a versioned recipe for building a package from source, such as a C or C++ library.
• 35 new ports were added to the curated registry.
• 517 ports were updated. As always, we validate each change to a port by building all other ports that depend on or are depended by the library that is being updated for our 15 main triplets.
• 132 community contributors made commits.
• The main vcpkg repo has over 6,900 forks and 25,100 stars on GitHub.

vcpkg changelog (2025.06.13 release)

The following notable changes were made in this release:

• Due to recent changes in GitHub Actions Cache’s API, the x-gha binary caching provider has been rendered obsolete. As a result, we had to remove it from vcpkg (PR: Microsoft/vcpkg-tool#1662). Instead, you can use one of the following methods to cache binaries in GitHub; we welcome any feedback from our users about how this experience could be improved in the future:
  • Use GitHub Packages with NuGet, which uses vcpkg’s caching mechanism and preserves caching granularity per port. This is the method the vcpkg team recommends.
  • Use actions/cache in your workflow to cache the installed directory. The downside of this method is that the whole installed tree gets cached as a single artifact, so single port updates invalidate all packages.
• Fixed a bug causing permissions while using upkg to not be preserved (PR: Microsoft/vcpkg-tool#1625).
• Improved diagnostics and bug fixes for vcpkg x-test-features command (PRs: Microsoft/vcpkg-tool#1649, Microsoft/vcpkg-tool#1650, Microsoft/vcpkg-tool#1663, Microsoft/vcpkg-tool#1676, thanks @autoantwort!).
• Fixed an issue causing slow binary cache insertions in some Docker containers (PRs: Microsoft/vcpkg-tool#1659, Microsoft/vcpkg-tool#1669, thanks @Thomas1664, @dg0yt!).
• Other minor bug fixes and internal feature improvements (thanks @autoantwort, @dg0yt, @huangqinjin, @DewJunkie!).

Documentation changes

• The vcpkg docs have moved to the MicrosoftDocs organization, under the URL https://github.com/MicrosoftDocs/vcpkg-docs. The existing repo has fully migrated with no loss in functionality. Links to the old repo should redirect to the new one automatically. The experience on the Learn website remains the same.
• Added documentation for the new commands format-feature-baseline and x-test-features (PR: MicrosoftDocs/vcpkg-docs#455).
• Added documentation for vcpkg license-report command (PR: MicrosoftDocs/vcpkg-docs#491).
• Updated Tutorial: Set up a vcpkg binary cache using GitHub Packages in a GitHub Actions workflow to clarify that mono is no longer pre-installed by default for GitHub Actions Ubuntu runners (PR: MicrosoftDocs/vcpkg-docs#495).
• Updated vcpkg in MSBuild projects article to add instructions about how to pass MSBuild properties to vcpkg builds (PR: MicrosoftDocs/vcpkg-docs#481).
• Removed documentation references to GitHub Actions Cache and x-gha provider, de-indexed the associated tutorial, and added a removal notice on the reference page.
• Other minor documentation improvements (thanks @Alan Pope, @Ivan Sorokin, @shijunz, @Tiago Freitas, @Yan Romao!).

If you have any suggestions for our documentation, please submit an issue in our GitHub repo or see the box at the bottom of a particular article.

Total ports available for tested triplets

While vcpkg supports a much larger variety of target platforms and architectures (as community triplets), the list above is validated exhaustively to ensure updated ports don’t break other ports in the catalog.

Thank you to our contributors

vcpkg couldn’t be where it is today without contributions from our open-source community. Thank you for your continued support! The following people contributed to the vcpkg, vcpkg-tool, or vcpkg-docs repos in this release (listed by commit author or GitHub username):

Learn more

You can find the main release notes on GitHub. Recent updates to the vcpkg tool can be viewed on the vcpkg-tool Releases page. To contribute to vcpkg documentation, visit the vcpkg-docs repo. If you’re new to vcpkg or curious about how a package manager can make your life easier as a C/C++ developer, check out the vcpkg website – vcpkg.io.

If you would like to contribute to vcpkg and its library catalog, or want to give us feedback on anything, check out our GitHub repo. Please report bugs or request updates to ports in our issue tracker or join more general discussion in our discussion forum.