`wingetcreate update` based on GitHub release

Open
#497 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
cli

Research direction

Start with the wingetcreate update command and the GitHub Releases REST API documentation linked in the issue. Compare the proposed --release-url and --repo/--tag entry points, including how tags map to versions. Done means defining and implementing the scope for extracting the version, Windows installer assets, and release notes from a GitHub release.

Written by the indexing model from the issue text.

Description

Issue-Feature
Description of the new feature / enhancement

it'd be great if it'd be possible to run wingetcreate update with a GH release URL where it'd then scrape all relevant information from there (extracting the version number, automatically scanning all assets for windows installers and picking all, grabbing the release notes (see also #103), and possibly more).

one option would be that the user passes the URL - e.g. wingetcreate update --release-url https://github.com/microsoft/winget-create/releases/tag/v1.5.7.0
the other would be to instead pass GH specific information - e.g. wingetcreate update --repo microsoft/winget-create --tag v1.5.7.0

this is maybe also related to #368 (though that was about the create use-case)

for reference: komac supports this acc. to their README.

Proposed technical implementation details

in either case of the suggested calling ways the wingetcreate update would internally probably then extract the necessary information using the GitHub REST API (docs for the releases API).

one issue with the version number (which is also why i proposed --tag above instead of re-using --version) is that the tag might not correspond 1:1 to the version number, e.g. v1.5.7.0 vs. 1.5.7.0 (though maybe a simple heuristic might be enough to cover >95% of all cases?).

Dominant language
C#
Stars
651
Forks
114
Avg merge
7h 52m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/winget-create

All issues in microsoft/winget-create

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.