You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, @sitiom! Big thanks for adding it to Winget and for maintaining it so far. I've installed Chafa from your distribution on several occasions :-)
The reason I haven't been adding binary releases to GitHub is that it adds complexity to the release process - it's just one more thing I need to keep on a checklist lest I forget to do it. I also prefer a single source for binaries because it's easier to guarantee security that way.
I've noticed some distributors pull the artefacts from the official website, and some have rules to detect when a new version has been dropped.
I have questions:
Does Winget have tooling to download from plain https repositories? If so, this may be a better option.
Do you know if it's theoretically possible to have the GH action that publishes to Winget download from the official website, instead of from the GH release?
Chafa was added to winget, but can there be an automated release instead? It would prevent the winget version from lagging behind the current release.
You could automatically push chafa GitHub releases to winget with a GitHub workflow.
In this repo you could create a GitHub Action that publishes to winget on a GitHub release.
Example: sxyazi/yazi#1299
Maybe @sitiom could help with this. He created published the original winget manifest.
The text was updated successfully, but these errors were encountered: