microsoft / microsoft/winget-pkgs

[Update Request]: LM Studio doesn't detect updates to build numbers (e.g. 11)

Open
#254,488 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Help-Wanted Issue-Task Package-Update
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

What type of update are you requesting?

A change to the package metadata

Current Package Identifier

ElementLabs.LMStudio

Package Version

0.3.15

Please describe the changes you would like to see

First off, I'm not very well versed in WinGet source code, so I have no idea what I'm talking about technically.

winget update did not show any updates available for LM Studio, but when opening the application I was prompted to update to the latest version, which was the same version number but Build 11, which is not a part of the version code in winget. I guess that makes winget not "see" that there's a change/new version available. Would be nice to be able to use winget to update between build numbers just like when using the in-app method. I guess that requires a change in how version numbers are currently formatted.

Again, I am not very familiar with how this all works, so bear with me if I am inaccurate or have misconceptions. Hope this can be improved without too much hassle!

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 package metadata for ElementLabs.LMStudio and how WinGet represents its version. Determine whether the Build 11 change can be represented in the package metadata and how update detection should recognize it. Done means the package can expose the newer build through WinGet without losing the existing version information.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.