Skip to content
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

Automate winget releases #242

Open
ykhan21 opened this issue Jan 16, 2025 · 3 comments
Open

Automate winget releases #242

ykhan21 opened this issue Jan 16, 2025 · 3 comments
Labels
dist Distribution (packaging, binary builds, etc)

Comments

@ykhan21
Copy link

ykhan21 commented Jan 16, 2025

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.

@hpjansson
Copy link
Owner

Thanks for suggesting this! It sounds like something we can do, but it'd be great to hear what the current publisher thinks first.

@hpjansson hpjansson added the dist Distribution (packaging, binary builds, etc) label Jan 16, 2025
@sitiom
Copy link
Contributor

sitiom commented Jan 16, 2025

In this repo you could create a GitHub Action that publishes to winget on a GitHub release.
Example: sxyazi/yazi#1299

Yes, that would work if only the stand-alone executables were available on the GitHub releases (which is not the case right now).

@hpjansson
Copy link
Owner

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dist Distribution (packaging, binary builds, etc)
Projects
None yet
Development

No branches or pull requests

3 participants