What’s New in vcpkg (Jul 2026)

This blog post summarizes changes to the vcpkg package manager as part of the 2026.07.29 registry release and the 2026-07-13, 2026-07-24, and 2026-07-27 tool releases. These updates include major SBOM improvements in vcpkg-tool, 302 updated ports including multiple major library upgrades, and other minor improvements and bug fixes.

• There are now 2,858 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.
• 16 new ports were added to the curated registry.
• 302 ports were updated in July. 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 main triplets.
• 93 community contributors made commits.
• The main vcpkg repo has over 7,700 forks and 27,300 stars on GitHub.

vcpkg changelog (2026.07.29 release)

• vcpkg-tool gained a set of SBOM improvements, including canonical vcpkg PURLs, corrected dependency snapshot relationships/correlators, and SPDX gitoids for Git trees, improving generated supply-chain metadata quality (PRs: Microsoft/vcpkg-tool#2049, Microsoft/vcpkg-tool#2072, Microsoft/vcpkg-tool#2073, Microsoft/vcpkg-tool#2074).
• Fixed Qt plugin deployment in z-applocal, improving post-build runtime deployment behavior for Qt-based apps (PR: Microsoft/vcpkg-tool#2048, thanks @vicroms!).
• Added CURL_CA_BUNDLE support and VCPKG_SSL_REVOKE_BEST_EFFORT, improving compatibility with curl-like certificate configuration and reducing Schannel proxy revocation failures on Windows (PRs: Microsoft/vcpkg-tool#2042, Microsoft/vcpkg-tool#2043, thanks @Matus-p and @sdn9002!).
• Added vcpkg print-usage with heuristic affirmation to improve package usage guidance output (PR: Microsoft/vcpkg-tool#2045).
• Improved robustness by handling broken-pipe stdout and POSIX .partial extraction directory collisions more safely (PRs: Microsoft/vcpkg-tool#2059, Microsoft/vcpkg-tool#2036, thanks @ricardoofnl and @Erik-White!).
• Notable port updates include grpc 1.76.0#1 -> 1.81.1, gstreamer 1.26.5#1 -> 1.28.4#1, sdl3 3.4.10#1 -> 3.4.12, mujoco 3.9.0 -> 3.10.0, and mongo-cxx-driver 4.3.1 -> 4.4.0.
• Additional major or high-impact updates include z3 4.16.0 -> 5.0.0, svt-av1 3.1.2#1 -> 4.1.0, libjpeg-turbo 3.1.4.1 -> 3.2.0, libffi 3.6.0 -> 3.7.1, and curl 8.21.0 -> 8.21.0#1.
• 7 ports were removed as part of ongoing registry maintenance: gsoap, json-spirit, nrf-ble-driver, opendnp3, sese, via-httplib, and xcb.
• Other minor improvements and bug fixes.

Documentation updates

• Documented default z-applocal behavior and legacy applocal fallback switches for CMake/MSBuild integration (PR: MicrosoftDocs/vcpkg-docs#581).
• Added vcpkg-tool README documentation into vcpkg docs (PR: MicrosoftDocs/vcpkg-docs#396).
• Improved docs consistency with CMake variable wording updates and formatting/capitalization fixes (PRs: MicrosoftDocs/vcpkg-docs#583, MicrosoftDocs/vcpkg-docs#582).

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 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.