-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[Feature][Track] publish package to winget #142
Comments
|
@manudss Thank you very much for your contribution. Can you tell me what command I need to execute if I want to write |
There seems to be a collision between this package and https://github.com/sonnylazuardi/chatgpt-desktop/. They both install to |
Hi, the version was already published, you can find it here : https://winstall.app/apps/lencx.ChatGPT The command to install is : |
@manudss Thanks, we've updated it in the readme. I have a question, there are two spaces before |
See information about this github actions here : https://github.com/marketplace/actions/winget-releaser ref : lencx#142
one space is enough. |
have a look at the github actions detail, and I think we encountered an error. |
Hi @yixinBC, sorry for the delay in response, I didn't have time to look before. It's an access problem, the Github token doesn't have the rights to access the repos:
|
@manudss token I have modified, just not released a new version to verify. |
The version 0.8 have already been published by someone else : microsoft/winget-pkgs#93238 |
The script is already working properly microsoft/winget-pkgs#93598 |
I fixed this by instructing an uninstall and then a reinstall:Installer failed with exit code: 1603 |
See information about this github actions here : https://github.com/marketplace/actions/winget-releaser ref : lencx#142
Feature description
this issue tracks #129
All updates about the winget-pkgs pr status and the implemention/development of auto-release scripts will be discussed here first.
Motivation
No response
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: