Paket outdated minor versions?
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
I would like to do "paket outdated" but only for minor-versions check-up.
Sometimes packages release important security updates to old versions too, not only supporting the latest version.
Let's take example package, let's say I'm using SwaggerProvider 0.12.1:
| Version, | Downloads, | Updated |
|---|---|---|
| 2.0.0-beta4 | 2,764 | 21/08/2022 |
| 1.0.1 | 11,212 | 25/06/2022 |
| 1.0.0 | 2,541 | 17/04/2022 |
| 0.12.2 | 3,484 | 25/06/2022 |
| 0.12.1 | 579 | 09/04/2022 |
The major version 1.0 has changed Newtonsoft.Json to System.Json which is a major migration for me, I don't want to re-test all serialization.
But I would still like to find the easy minor-update.
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 with the paket outdated command and its version-selection behavior. Clarify how a minor-version-only check should handle packages whose latest releases require a major migration, using the SwaggerProvider example as a reference. Done means the command can report compatible minor updates without requiring major-version upgrades.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100