GitHub dependencies do not disappear from the lock file after they are removed
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
I believe that the title is self-descriptive. Moreover, the entry in paket.lock stays the same even after the branch or the commit hash are explicitly changed in paket.dependencies.
Reproduction steps
Please provide the steps required to reproduce the problem
-
Add a GitHub dependency.
-
paket install -
Remove it.
-
paket install
Expected behavior
paket.lock does not state the now-removed GitHub dependency.
Actual behavior
The dependency still exists in paket.lock.
Known workarounds
Manually edit paket.lock.
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
Reproduce the issue with a GitHub dependency using the listed paket.dependencies and paket install steps, then inspect the resulting paket.lock. Trace how removal or branch and commit-hash changes are handled, and consider the work complete when paket.lock no longer contains the removed or outdated GitHub dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp, github
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100