microsoft / microsoft/OSSGadget
Update how versions work in the project managers.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 371
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
So one of the issues I have come across while testing various managers is that in some cases semantic versioning convention is not being followed.
For example, pkg:pypi/plotly@0.2 is an invalid semver because 0.2 doesn't fit the semantic version specs.
And in another even weirder example pkg:composer/ircmaxell/random-lib@dev-cipher_mixer where the version dev-cipher_mixer isn't even close to the semantic version spec.
As far as I can tell, there isn't really a need for the versions to ever be in any kind of order, and the only reason why we ever order it is to get the latest version. So if we separate the logic out for that from relying on EnumerateVersionsAsync then we could probably make this work.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the project-manager implementations and reading EnumerateVersionsAsync, which the issue identifies as the current source of ordering behavior. Confirm how non-semver versions such as 0.2 and dev-cipher_mixer are handled, then verify that accepting them does not prevent selecting the latest version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100