New version: Cloudflare.Warp version 25.1.861.0#231884
Conversation
|
/AzurePipelines run |
|
Automatic Validation ended with:
(Automated response - build 981.) |
|
/AzurePipelines run |
|
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
| UpgradeCode: '{1BF42825-7B65-4CA9-AFFF-B7B5E1CE27B4}' | ||
| Installers: | ||
| - Architecture: x64 | ||
| InstallerUrl: https://1111-releases.cloudflareclient.com/windows/Cloudflare_WARP_Release-x64.msi |
There was a problem hiding this comment.
Can't we use fixed URL again? This URL is unstable. ref: #213644
There was a problem hiding this comment.
This is what we sometimes call a "vanity URL", as it always serves the latest version of the package. We have automation to update these, when a hash mismatch is detected. And the community has an ongoing debate about which type of link should be used, as both have advantages and disadvantages.
There was a problem hiding this comment.
Hello,
I think dynamic is better than vanity. I apologize that my automation kicked off the vanity url again.
There was a problem hiding this comment.
Thank you for sharing it with me. I didn't know it is called vanity URL. Personally, I avoid vanity URLs for all packages. Perhaps including both vanity and fixed URLs might be better, like Google.Chrome (vanity) and Google.Chrome.EXE (fixed).
Pull request has been created with komac v2.10.1 🚀
Microsoft Reviewers: Open in CodeFlow