Describe the bug
Calling YamlCreate.ps1 script with parameters does not work properly. The way I tried to call the script can be seen in these commits (693189d, 5abe8c2) and the result can be in the logs of workflow runs #47, #48, #49.

Expected behavior
YamlCreate should get parameters and does not prompt for select mode, package identifier, etc...

Additional context
Add any other context about the problem here.

List the PackageIdentifier of the package to be added to automation

Appest.TickTick

Details about the application

1. Use $result.version to get and check the version
   https://pull.ticktick.com/windows/release_note.json
2. Get the installer URL from download link, along with getting installer file
   If only the url is needed, you can use HEAD method for webrequest to avoid fetching full response.

   $webrequest = Invoke-WebRequest 'https://ticktick.com/static/getApp/download?type=win64'
   $installerurl = $webrequest.BaseResponse.RequestMessage.RequestUri.OriginalString

List the PackageIdentifier of the package to be added to automation

Anaconda.Anaconda3

Details about the application

From Evergreen: https://github.com/aaronparker/Evergreen/blob/main/Evergreen/Manifests/Anaconda.json

List the PackageIdentifier of the package to be added to automation

360.360zip

Details about the application

https://yasuo.360.cn/update/versioninfo.json

$result.data.winCode PackageVersion
And use the version to fill in the following url
https://down.360safe.com/360zip_setup_$($version).exe
e.g. https://down.360safe.com/360zip_setup_4.0.0.1360.exe

List the PackageIdentifier of the package to be added to automation

Tencent.Weiyun

Details about the application

x64 version:
https://dldir1.qq.com/weiyun/electron-update/release/x64/latest.yml
Append the file name to https://dldir1.qq.com/weiyun/electron-update/release/x64/ to get the InstallerUrl.
e.g. https://dldir1.qq.com/weiyun/electron-update/release/x64/WeiyunApp-Setup-X64-5.2.1140.exe

x86 version:
https://dldir1.qq.com/weiyun/electron-update/release/win32/latest-win32.yml
Append the file name to https://dldir1.qq.com/weiyun/electron-update/release/win32/ to get the InstallerUrl.
e.g. https://dldir1.qq.com/weiyun/electron-update/release/win32/WeiyunApp-Setup-WIN32-5.2.1140.exe

List the PackageIdentifier of the package to be added to automation

Microsoft.Edge*

Details about the application

No response

Is there an existing issue for this?

• I have searched the existing issues

What happened?

In the automation, the tag is being explicitly compared to see if it is greater than the previously checked tag to determine if an update is needed. However, it isn't guaranteed that the tag will be sanitized for the comparison.

Consider the example:

LastCheckedTag: v2.0.1
Tag: 3.0.0

Something as simple as a repository owner forgetting a character can lead to versions being missed. However, since the package could use result.tag_name.TrimStart('v') to get the version, there isn't a reason that it should be missed.

Potential Fix

Instead of the last checked tag, fetch and store the last checked release ID (result.id). Since this is autogenerated by github, it is should always be greater for newer releases. The tag can still be used to fetch the version number, but doesn't need to be stored

I know this won't work for the custom script packages and non-git packages, but there the version can be used instead still

Is there an existing issue for this?

• I have searched the existing issues

What happened?

While generating manifests, product code is not automatically detected from the installer.

List the PackageIdentifier of the package to be added to automation

Glodon.CADReaderInternational

Details about the application

API:
https://cadreader.glodon.com/query/update/cadpc?clientVersion=$($version)&cadpcClientBits=32
e.g. https://cadreader.glodon.com/query/update/cadpc?clientVersion=3.4.3.12&cadpcClientBits=32

$result.data.url InstallerUrl
$result.data.version PackageVersion

What would you like to see changed/added?

ARP data of a package should be validated before submitting PRs.

What would you like to see changed/added?

Summary

Some packages may not need to be checked for updates daily. It would be possible to have the runs be faster if not every package were checked every single time.

Idea

Add a LastCheckedTimestamp field and a CheckIntervalSeconds field to the json files. If the current timestamp is less than the last checked timestamp + the check interval, skip the package

Is there an existing issue for this?

• I have searched the existing issues

What happened?

https://github.com/vedantmgoyal2009/winget-pkgs-automation/blob/main/packages/s/sohu.shplayer.json

https://github.com/vedantmgoyal2009/winget-pkgs-automation/runs/3917107960?check_suite_focus=true#step:3:911

List the PackageIdentifier of the package to be added to automation

TomWatson.BreakTimer

Details about the application

https://github.com/tom-james-watson/breaktimer-app

What would you like to see changed/added?

I would suggest there be a script that runs any time a new package is added to automation. It can be triggered based on when a new .json file is created in the /packages folder

This script would fetch ALL the previous releases and attempt to add them to winget-pkgs. That way, as many versions of an application are available as possible

List the PackageIdentifier of the package to be added to automation

Alibaba.DingTalk

Details about the application

https://im.dingtalk.com/manifest/new/release_windows_vista_later_manual_lowpriority.json

$result.win.install.url InstallerUrl
$result.win.install.version PackageVersion

Describe the bug
Because installer architecture and number of URLs mismatch, wingetcreate does not update many packages.

Expected behavior
All packages should be updated.

Additional context
Migrate from wingetcreate to YamlCreate.ps1 script because it has better options.

Is there an existing issue for this?

• I have searched the existing issues

What happened?

https://github.com/vedantmgoyal2009/winget-pkgs-automation/blob/main/packages/o/olivia.via.json

List the PackageIdentifier of the package to be added to automation

AcFun.AcFunVirtualTool

Details about the application

API:
https://api.kuaishouzt.com/rest/zt/appsupport/checkupgrade?appver$($version)&kpn=ACFUN_APP.LIVE.PC&kpf=WINDOWS_PC
Example: https://api.kuaishouzt.com/rest/zt/appsupport/checkupgrade?appver=1.16.0.598&kpn=ACFUN_APP.LIVE.PC&kpf=WINDOWS_PC

$result.releaseInfo.downloadUrl InstallerUrl
$result.releaseInfo.version PackageVersion

List the PackageIdentifier of the package to be added to automation

ByteDance.JianyingPro

Details about the application

Source:
https://lf3-beecdn.bytetos.com/obj/ies-fe-bee/bee_prod/biz_80/bee_prod_80_bee_publish_3563.json

$result.windows_download_pkg.channel_default InstallerUrl
And use InstallerUrl to generate PackageVersion.

List the PackageIdentifier of the package to be added to automation

1MHz.Knotes

Details about the application

https://knotes2-release-cn.s3.amazonaws.com/win/latest.yml

And append the file name to https://knotes2-release-cn.s3.amazonaws.com/win/
e.g. https://knotes2-release-cn.s3.amazonaws.com/win/Knotes%20Setup%202.11.2.exe

List the PackageIdentifier of the package to be added to automation

TimKosse.FileZilla.Client TimKosse.FileZillaClient

Details about the application

From Evergreen:
https://github.com/aaronparker/evergreen/blob/main/Evergreen/Manifests/FileZilla.json

Is there an existing issue for this?

• I have searched the existing issues

What happened?

Labeler workflow only succeeds on repository owner's pull request and fails on contributors PR.

Add more details about the project and how it works.

List the PackageIdentifier of the package to be added to automation

Unicorn.PaintAid

Details about the application

http://pa.udongman.cn/index.php/upgrade/

Combine //updater/win_mversion and //updater/win_subversion with a . to get the version.
e.g. 2.1 + . + 1.0 → 2.1.1.0
Append //updater/TypeWin/package/name to //updater/TypeWin/package_url to get the url.
e.g. http://s.udongman.cn/paintaid/32/HHZS.2.1.1.0.20210924.win.exe

@allcontributors

Is there an existing issue for this?

• I have searched the existing issues

What happened?

The repo uri for surgesynth.surge is not valid and the releases have moved https://github.com/surge-synthesizer/surge/releases

I believe the new URI is https://github.com/surge-synthesizer/releases/releases/tag/1.9.0/

List the PackageIdentifier of packages to be added to automation

• GithubPackages.csv

List the PackageIdentifier of the package to be added to automation

Baidu.BaiduNetdisk

Details about the application

Source:
https://pan.baidu.com/disk/cmsdata?do=client

$result.guanjia.url InstallerUrl
$result.guanjia.version PackageVersion (Regex or slicing is needed for parsing)

List the PackageIdentifier of packages to be added to automation

• Add all JetBrains Products to automation.

Mentioning @jedieaston since he mostly updates JetBrains products.

List the PackageIdentifier of the package to be added to automation

calibre.calibre_portable

Details about the application

An easily transferrable version of the calibre application.

calibre is a powerful and easy to use e-book manager. Users say it’s outstanding and a must-have. It’ll allow you to do nearly everything and it takes things a step beyond normal e-book software. It’s also completely free and open source and great for both casual users and computer experts.

List the PackageIdentifier of the package to be added to automation

Bilibili.Livehime

Details about the application

Source:
https://api.live.bilibili.com/client/v1/LiveHime/download?type=3

$result.data.dl_url InstallerUrl
$result.data.version PackageVersion (Take the last part)

List the PackageIdentifier of the package to be added to automation

OctopusDeploy.Server

Details about the application

No response

List the PackageIdentifier of the package to be added to automation

LeiGod.LeiGodAcc

Details about the application

Source: https://jiasu.nn.com/configs.json

InstallerUrl: $result.windows.download_url
PackageVersion: RegEx from Url

PR - microsoft/winget-pkgs#29801

List the PackageIdentifier of the package to be added to automation

CrowTranslate.CrowTranslate

Details about the application

https://github.com/crow-translate/crow-translate

List the PackageIdentifier of the package to be added to automation

Sohu.SHPlayer

Details about the application

API:

"https://p2p.hd.sohu.com.cn/update?clienttype=3&version=$($version)"

e.g. https://p2p.hd.sohu.com.cn/update?clienttype=3&version=7.0.3.0

$result.version PackageVersion
$result.cdn InstallerUrl

List the PackageIdentifier of the package to be added to automation

Adobe.AdobeAcrobatReaderDC

Details about the application

No response

Add the following key to all the JSONs:

"is_prerelease": false

Note: Some packages may already contain "is_prerelease": true, so they should be skipped.

List the PackageIdentifier of the package to be added to automation

Thunisoft.HuayuPY

Details about the application

https://pinyin.thunisoft.com/webapi/v1/setup/setupinfo?os=win

List the PackageIdentifier of the package to be added to automation

Baidu.BaiduTranslate

Details about the application

https://fanyiapp.cdn.bcebos.com/fanyi-client/update/latest.yml

Well, I previously thought that I would update SourceForge packages using RSS feeds but since I have now found a better and easy way to update them, I would be adding them to the automation.

@Trenly Can you share the script with which you bulk-generated JSONs for GitHub packages? I think, by changing it a little, I can generate JSONs for packages updated via SourceForge.

@OfficialEsco @jedieaston @ItzLevvie Can you all please suggest some packages which are shipped through GitHub releases so that I can them in packages.json?

List the PackageIdentifier of the package to be added to automation

Tencent.TencentDocs

Details about the application

https://dldir1.qq.com/weiyun/tencentdocs/electron-update/release/latest-win32.yml

Append url or path to https://dldir1.qq.com/weiyun/tencentdocs/electron-update/release to get the InstallerUrl.

List the PackageIdentifier of the package to be added to automation

kapitainsky.RcloneBrowser

Details about the application

GitHub: https://github.com/kapitainsky/RcloneBrowser/releases

Pull Request: microsoft/winget-pkgs#30733

List the PackageIdentifier of the package to be added to automation

Moonsworth.LunarClient

Details about the application

Source: https://launcherupdates.lunarclientcdn.com/latest.yml

PR - microsoft/winget-pkgs#31164

List the PackageIdentifier of the package to be added to automation

OctopusDeploy.Tentacle

Details about the application

No response

Description of issue

Using a file such as packages.json is not a sustainable method for passing in large numbers of packages. As the number of packages to update is likely to grow into the hundreds, a more sustainable solution should be used.

Proposed solution

Use the same manifest structure as winget-pkgs, having a json file for each individual package. You can then use Get-ChildItem -Recurse to fetch all of the packages. With this, you can then use a process block within your function to process the items in a more structured manner.

Another benefit of using individual json files for this would be that the script is more resilient against errors. If an error occurs while writing to the file, it won't effect other packages. It will also make it so that the script could be run for just a specific subset of packages

Is there an existing issue for this?

• I have searched the existing issues

What happened?

My team owns and manages deployments for the Microsoft.Git, Microsoft.GitCredentialManagerCore, and Microsoft.VFSforGit. We would like these packages to be removed from this repo's packagest.txt, as we are currently in the process of transitioning to using microsoft/wingetcreate for automatically generating/submitting new manifests with the appropriate structure.

Describe the feature/enhancement you'd like

• Support for auto-updating packages from SourceForge [DONE] - e.g. Freeplane
• Support for auto-updating packages from RSS feeds.
• Check if a PR has been opened before submitting Pull Request via automation [DONE] - Implemented in YamlCreate.ps1 Trenly/winget-pkgs#69

Proposed technical implementation details (optional)
Found a way, will be implementing soon.

Additional context
https://gist.github.com/OfficialEsco/599257140346fa4a79b36dc63bb20d61 (from https://github.com/vedantmgoyal2009/winget-pkgs-automation/issues/1#issuecomment-927286125)

Describe the bug
Balena.BalenaCLI was updated automatically but the package json was not updated microsoft/winget-pkgs#28985

Expected behavior
A clear and concise description of what you expected to happen.
Json file should be updated when the package PR is created

Additional context
https://github.com/vedantmgoyal2009/winget-pkgs-automation/blob/main/packages/b/balena.balenacli.json

List the PackageIdentifier of the package to be added to automation

BlueJTeam.BlueJ

Details about the application

From Evergreen:

• https://github.com/aaronparker/evergreen/blob/main/Evergreen/Apps/Get-BlueJ.ps1
• https://github.com/aaronparker/evergreen/blob/main/Evergreen/Manifests/BlueJ.json