Acrobat Pro winget manifest updates the manifest too slowly

I guess 2 different teams manage the update cycle and the winget manifest files and they don’t talk to each other.

RIght now, the manifest points to a “vanity URL” that never changes to download the package (winget-pkgs/manifests/a/Adobe/Acrobat/Pro/26.001.21529/Adobe.Acrobat.Pro.installer.yaml at master · microsoft/winget-pkgs · GitHub)

But when a new version of adobe pro comes out, the SHA256 hash changes, and winget gets a hash mismatch. Adobe reader has no issue from that since you actually point to a different URL every version (as it should be), but your paying customers are left behind for software installation/automation. This is such a weird thing to see.

There is no “feature request” for acrobat pro, so I guess I’ll ask this here

Either create new packages and update the manifest, keeping your old manifest versions like you do for adobe reader, or update the SHA256 hash whenever you release a new version.

Please.