microsoft / microsoft/winget-pkgs

[New Feature]: Have Wingetbot try to match the version formatting

Open
#34,421 5 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Bots Issue-Feature Moderator-Approved
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

Description of the new feature/enhancement

This idea is based from these PR's, among others:

I propose that @wingetbot should try to pattern match whatever version it detects to the package version which already exists in the repo. This would allow the bot to be self-correcting in the cases where the tag or published version is of a different string format than the one in ARP.

This may also be something to consider along with microsoft/winget-create#203

Proposed technical implementation details (optional)

I know it would take a lot of work, but it should be possible to do string interpolation like this. Alternatively, if the bot had an environment to install the application and pull directly from ARP, that would avoid the issue entirely.

Examples:

Found Version Previous Version Version to use
3.89.12.1805 3.89.9 3.89.12
4.13.19.21804 4.12.23 4.13.19
2020-12-5-1388 20.11.15.1182 20.12.5.1388

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.

Research direction

Start by reviewing the linked winget-pkgs pull requests and microsoft/winget-create#203 to understand the version-formatting cases and existing discussion. Done means Wingetbot can match detected versions to the repository's existing package version format, including the examples in the issue.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.