Can confirm this solves my issue.

If non-release revisions of vcpkg aren't stable we should probably only use released versions. (If I checked correctly you aren't updating to the latest release: 2024.09.23.) (Also disregard my comment if the fix isn't available in that release, but in this case we might want to ask them to backport it 🤔)

but in this case we might want to ask them to backport it 🤔

To an existing release? Releases/git tags are immutable, and I doubt they'd create a point release just for our tiny problem.

Looks like we are already using an arbitrary commit, so this looks okay.

The commit message made me think it was related to vcpkg itself, not a library. I agree that it actually doesn't make sense to backport the fix we want.

Looks like we are already using an arbitrary commit, so this looks okay.

The last time we updated was the first time we used an arbitrary commit. My point was that if we see problems with vcpkg itself when living closer to head, we should probably not do that. But anyway, this isn't the case, so yeah, it looks okay. And sorry for the noise.