Unexpected input(s) 'vcpkgArguments', 'vcpkgTriplet'

[Coeur]

windows-vs-job shows this warning:

(https://github.com/libevent/libevent/actions/runs/8949929874/job/24584751215#step:4:1)
Unexpected input(s) 'vcpkgArguments', 'vcpkgTriplet', valid inputs are ['vcpkgDirectory', 'runVcpkgInstall', 'vcpkgGitCommitId', 'vcpkgGitURL', 'doNotUpdateVcpkg', 'doNotCache', 'vcpkgJsonGlob', 'vcpkgJsonIgnores', 'vcpkgConfigurationJsonGlob', 'binaryCachePath', 'runVcpkgFormatString', 'useShell', 'logCollectionRegExps']

This may be a result from 3e01178 which updated the job while leaving the existing inputs?
I do not know the replacements for 'vcpkgArguments' and 'vcpkgTriplet'.

Current action looks like that:

libevent/.github/workflows/build.yml

Lines 267 to 274 in 5d45f4d

	- name: Prepare vcpkg
	uses: lukka/run-vcpkg@v11
	id: runvcpkg
	with:
	vcpkgArguments: zlib:x64-windows openssl:x64-windows mbedtls:x64-windows
	vcpkgDirectory: ${{ runner.workspace }}/vcpkg/
	vcpkgTriplet: x64-windows
	vcpkgGitCommitId: c8696863d371ab7f46e213d8f5ca923c4aef2a00 # 2023.12.12

[fanquake]

@hebasto you might have an idea?

[hebasto]

The lukka/run-vcpkg versions newer than v7 expect a vcpkg manifest file.

The most direct fix is to revert its version back to v7. The concerns expressed in 3e01178 are supposedly mitigated in the recent v7.6 release.

The other option is to introduce a vcpkg.json manifest file.