
Get reproducible builds independent from the current state of the vcpkg ports registry.Conveniently upgrade all declared dependencies at once via baselines.Freeze dependencies at specific versions.Declare minimum version constraints on dependencies.Today, we are announcing support for another anticipated feature: Package versioning. Two such features are manifests and binary caching, which we announced some time ago, and users have been successfully using them in their projects since then. Please give us your feedback and let us know how we can improve.įor the past year we have been focusing our efforts on implementing highly requested features in vcpkg that will help our users in a wide variety of scenarios. For now, we are considering this feature experimental. The versioning feature is completely optional – you can choose not to specify library versions, and vcpkg will pick the most appropriate set of compatible versions for your dependencies from its baseline catalog. Versioning is not currently available for libraries installed via the command line (i.e.

In order to use this feature, a vcpkg.json manifest file must be present in your repo to declare dependencies. We have an exciting new feature to announce in vcpkg: the long-awaited and highly requested package versioning! This feature makes it possible to install specific versions of dependencies and control installed versions over time.

Special thanks to Victor Romero for putting together the content for this blog post.
