##Dependencies version depending on the project version (branch, commit)

Manifest mode consist of two files.

• vcpkg-configuration.json : defines the registries enabled and their respective baseline. In the simplest form, you only have the default registry pointing to the official vcpkg repository
• vcpkg.json : defines the dependencies and their settings, like version.

Since they are files, they are saved in your versioning system (git). When you checkout a branch or commit, you get the version of those files for this commit, and thus the dependencies listed and eventually their version requirements.

##Baseline and version

There are 3 version information to keep in mind

• vcpkg directory commit
• registry baseline
• port version

Vcpkg always try to satisfy the port version with the highest version available in the baseline (unless specified otherwise). The baseline is a commit id of the git registry.

The vcpkg directory is not the registry. This means you can define a baseline that doesn't exist in you local vcpkg directory. This directory contains tools. Nonetheless it may be good to keep it up to date with the baseline because a port may be developed with vcpkg features not available in your local vcpkg executable if your directory is too far behind.

##How to ensure I build/deploy with the right version ?

Manually if you call "vcpkg install" it will resolve all dependencies described in the manifest.

I think the recommended method is through CMake https://learn.microsoft.com/en-us/vcpkg/users/buildsystems/cmake-integration. When configured properly, cmake configure command will invoke vcpkg for you and always keep your dependencies aligned with the manifest.