vcpkg refuses to use binaries from GitLab NuGet feed due to ABI mismatch

[ashikdas-MobileCastle]

I have the following setup for developer machines:

VCPKG_INSTALL_OPTIONS=--only-binarycaching
VCPKG_BINARY_SOURCES=clear;nugetconfig,D:\NuGet.Config,read

• One developer (or CI) has readwrite access to the GitLab NuGet Package Registry and successfully uploads all built binaries.
• All other developers have read-only access to the same NuGet feed.

Problem:
When the read-only developers build the project in Visual Studio 2022, vcpkg refuses to use the existing binaries because the ABI hash differs from their local environment (different MSVC, SDK, or CMake versions).

I do not want developers to rebuild binaries locally because that takes a lot of time — for example, building gRPC and its dependencies can take hours — but I also do not want to strictly enforce identical tool versions across all developer machines.

Question:
Is there a way to skip ABI hash matching and instead reuse binaries based only on package name and version?

[Osyotr]

--x-abi-tools-use-exact-versions and VCPKG_DISABLE_COMPILER_TRACKING might help to reduce the amount of rebuilds.