-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New version: Google.Chrome.Canary version 97.0.4670.2 #30443
New version: Google.Chrome.Canary version 97.0.4670.2 #30443
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The installer hash is the same every day since that version of the Chrome installer just downloads the latest version.
Can you modify your script so that you just change the folder name and PackageVersion
instead of making new manifests every day (and leaving the old ones which don't work)? Then we don't have to do it in separate PRs.
I've been previously thinking about it but Trenly#37 and Trenly#57 are already in the queue for the next version of YamlCreate so if we can wait for a few days, we can get the feature in YamlCreate.ps1 itself. |
Possible duplicate package entry. Similar installer SHA256 hash found in manifest:
|
Hello @wingetbot! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
Hello @vedantmgoyal2009, |
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
Auto-updated by vedantmgoyal2009/winget-pkgs-automation
Microsoft Reviewers: Open in CodeFlow