paket install/update triggers an unwanted dotnet restore
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Since the 7.0.2 version the install or update command will trigger a dotnet restore command. This behaviour does not fit in our integration pipeline.
Repro steps
Just run paket install or paket update on a .NET solution.
Expected behavior
We would like to run a paket install without a dotnet restore triggering. It would be great to be able to disable it with a setting.
Actual behavior
paket install triggers an unwanted dotnet restore.
Known workaround
Add version 6.2.1 at the top of the paket.dependencies file in our .NET solution since this behaviour did not occur in this previous version.
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 reproducing paket install and paket update on a .NET solution and compare the behavior with the 6.2.1 workaround described in the issue. Trace where these commands trigger dotnet restore and identify the existing settings path before deciding how the opt-out should work. Done means a setting can prevent the restore while install and update continue to function.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100