[Update Request]: Microsoft.VCRedist.2015+.x64 update to 14.51.36231

[novinxy]

What type of update are you requesting?

A new version of an existing package

Current Package Identifier

Microsoft.VCRedist.2015+.x64

Package Version

14.51.36231

Please describe the changes you would like to see

There is new version available, see #374584 374584

Here is link to the package
https://download.visualstudio.microsoft.com/download/pr/c1bd4f2c-3672-468e-8480-7ed419dbb641/90E48ADE404E4576D023ABFA374F323555F233982A8805EA9AC63DCA9491A16B/VC_redist.x64.exe

[R-Adrian]

+1
i still don't know why WinGet doesn't use the already-published-by-Microsoft generic URLs for these redists... probably because automating file hash changes for a static / vanity URL is not allowed for Microsoft software without manual validation?

https://aka.ms/vc14/vc_redist.x64.exe
https://aka.ms/vc14/vc_redist.x86.exe
https://aka.ms/vc14/vc_redist.arm64.exe

[novinxy]

Isn't that becuase those pages are just redirects ? In few months it will redirect to newer version and break current installing older versions

[R-Adrian]

redirects / file hash changes can be handled by WinGet - see Anydesk for example
https://github.com/microsoft/winget-pkgs/tree/master/manifests/a/AnyDesk/AnyDesk

what i think it happens here is that they probably require manual confirmation / validation of changes to Microsoft software.

[R-Adrian]

update: i found the ACL - seems that only these authors are allowed to push changes / validate stuffs for the named packages:

https://github.com/microsoft/winget-pkgs/blob/master/Tools/ManualValidation/Auth.csv

[SpecterShell]

My automation bot is in charge of these packages. Previously, I used the Visual Studio manifest to monitor updates for VC redist, which seems to stop working a few weeks ago, possibly due to flaws in my codes, or because the VC redist in the manifest became outdated. I just updated the automation scripts and manually created PRs for the new versions.

---

i still don't know why WinGet doesn't use the already-published-by-Microsoft generic URLs for these redists... probably because automating file hash changes for a static / vanity URL is not allowed for Microsoft software without manual validation?

redirects / file hash changes can be handled by WinGet

Vanity URL is allowed, but a versioned URL is preferred over the vanity URL, as it won't

break current installing older versions

before the new PR gets merged.

---

what i think it happens here is that they probably require manual confirmation / validation of changes to Microsoft software.

There is no such rule AFAIK.

My automation bot is in charge of many Microsoft's packages, whilst I'm not affiliated to Microsoft anyway.