[Question/Optimization] How paket.exe update package_id --filter should work
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Hi,
We have a project(s) with around > 100 nuget packages. The update process for all of them tooks ~2minutes. Most of them are pinned to the specific version.
Is it possible to update only specific package and just check whether it's dependencies are fullfilled?
I've tried the following commands:
.paket\paket.exe update Newtonsoft.Json
and
.paket\paket.exe update Newtonsoft.Json --filter
It actually update a package, but after that it checks all other packages which are pinned to the specific version.
We need to execute an update command each time its built on our CI server to ensure we have a newest version (our internal company's library).
The question: should update with --filter argument resolve other packages?
Best regards,
MiloszeS
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.exe update command and its --filter option, then reproduce the behavior using Newtonsoft.Json alongside packages pinned to specific versions. Confirm whether filtered updates should still resolve those packages; done means the expected resolution scope is established and any resulting behavior is validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100