Luca

@BurningEnlightenment what about this simplified solution: if the newly added `vcpkgConfigurationGlob` input is provided, the glob expression (i.e., its value) is used to locate the `vcpkg-configuration.json` file: - if found,...

You may want to test out `run-vcpkg@dev/vcpkgconfjson-support`. Still more testing/validation and docs should be added, but the functionality should be there. Feedback is appreciated. Note: currently when `vcpkgGitCommitId` is not...

@BurningEnlightenment thank you, pushed the fix along with other doc changes and unit testing. It still needs a end to end validation of the feature.

@BurningEnlightenment I think that what is currently missing is the `builtin-baseline` in vcpkg.json (it is searching the one in `vcpkg-configuration.json` only). And probably also there are other cases to be...

@equeim @BurningEnlightenment @Shatur @jwillemsen please have a look at the changes in this PR and comment on the description: https://github.com/lukka/run-vcpkg/pull/216 I'd like your review on how the baseline is searched...

Solved in https://github.com/lukka/run-vcpkg/releases/tag/v11.4

@Shatur at the moment that is by design: if multiple `vcpkg.json`'s are in the filesystem repo subtree, `run-vcpkg` won't make a choice, but it expects the user to make it....

@bigerl @burningenlightment could you give a try with `get-cmake@dev/user_provided_versions`, published in this PR #53 e.g. ```yaml - uses: lukka/get-cmake@dev/user_provided_versions with: cmakeVersion: 3.22.6 ninjaVersion: 1.10.0 ````

@bigerl @BurningEnlightenment this feature is implemented in latest release: https://github.com/lukka/get-cmake/releases/tag/v3.24.3

@quyykk i think this issue could be solved since the addition of GHA to vcpkg, let me know! Thanks for your work! Solved by this release: https://github.com/lukka/run-vcpkg/releases/tag/v11.0