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

GitHub Release Automation #1184

Closed
RichiCoder1 opened this issue May 26, 2020 · 8 comments
Closed

GitHub Release Automation #1184

RichiCoder1 opened this issue May 26, 2020 · 8 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Milestone

Comments

@RichiCoder1
Copy link

RichiCoder1 commented May 26, 2020

Description of the new feature/enhancement

Somewhat spitball of an idea, but it'd be nice to automate going from a GitHub Release -> Winget-pkgs Pull Request. A lot of OSS distributes binaries via GitHub Releases now, so it'd be one less step for them to be able to map releases.

Proposed technical implementation details

I'm not sure TBH. The ability to configure a GitHub Project + an asset -> manifest mapping, and then a Msft service that polled those endpoints respectfully and created PRs on new releases?

@RichiCoder1 RichiCoder1 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label May 26, 2020
@dfreilich
Copy link

Great idea! It seems like there's more traction on dealing with this in #500

@denelon denelon added the Area-Validation-Pipeline Issues related to the manifest validation pipeline. label Jan 6, 2021
@ghost ghost added the No-Recent-Activity No activity has occurred on this work item for seven days. label Jan 13, 2021
@ghost

This comment has been minimized.

@denelon denelon removed the No-Recent-Activity No activity has occurred on this work item for seven days. label May 21, 2021
@denelon
Copy link
Contributor

denelon commented May 21, 2021

We have a new tool coming very soon (think days, not weeks) that will help with this issue. microsoft/winget-cli#157 we will include a standalone .exe you can include in CI pipelines to create/submit manifests and new package versions.

@denelon denelon added this to the v1.0 - Packages milestone May 21, 2021
@denelon denelon removed the Area-Validation-Pipeline Issues related to the manifest validation pipeline. label May 21, 2021
@denelon
Copy link
Contributor

denelon commented May 26, 2021

Here is the link to the new wingetcreate tool designed to help build manifests. The PR is in progress so soon you will be able to winget install wingetcreate.

@SonOfDiablo
Copy link

I'm not sure if this applies 100% to this issue.

But other package managers has great ways of handling manifest updates, such as Scoop's Autoupdate.

Could be worth looking into for inspiration.

@denelon denelon modified the milestones: v1.1-Packages, v.Next-Packages Sep 16, 2021
@denelon
Copy link
Contributor

denelon commented Sep 17, 2021

@SonOfDiablo we would prefer Independent Software Vendors (ISVs) and publishers to produce their own manifests. The wingetcreate utility can run as an .exe in a GitHub action to generate and submit manifests. The secondary option would be to "self-serve" GitHub releases. We've added a ".package" file for #100 and I think we could extend that functionality for this scenario.

@denelon
Copy link
Contributor

denelon commented Oct 4, 2021

@vedantmgoyal2009 as we get closer to having the ability to add a .packages file to support "pull" style automation vs. "push" from a publisher, we might be able to leverage some of the the work you've done. Thanks for building it open source under MIT license. That makes it much easier for us to look at how we might integrate this work into the Windows Package Manager app repository.

@denelon
Copy link
Contributor

denelon commented Nov 1, 2023

I think this issue could have been closed a while back. There are a few different automated options available.

Here are a couple of examples using wingetcreate:

@denelon denelon closed this as completed Nov 1, 2023
@denelon denelon modified the milestones: v.Next-Pipelines, 1.7 Packages Nov 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Projects
None yet
Development

No branches or pull requests

4 participants