Pin a VNU release instead of picking latest.

[meisterT]

Looks like they had a release today and that might be the reason for our test failures.

[vmcj]

I rather not pin as they seemed to not release often so it's more of a hassle to check manually

[meisterT]

IMO, pinning versions is best practice to avoid errors like this one.

But I will not fight for it if you dislike pinning. However, let's be pragmatic and merge this PR and then separately fix whatever changed at HEAD so that other PRs can be merged in the meantime.

[vmcj]

IMO, pinning versions is best practice to avoid errors like this one.

But I will not fight for it if you dislike pinning. However, let's be pragmatic and merge this PR and then separately fix whatever changed at HEAD so that other PRs can be merged in the meantime.

I think for components which upgrade often pinning is fine as I tend to check those often and upgrade them when needed. IRC this component does not often so I rather accept a day like today where we need to fix CI instead of having the check often with no new release. Especially for VNU I hope they finally implemented the current "accepted" spec for some elements so we can remove a couple of warnings as it tends to be very conservative.