Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add version number to paket.restore.targets
See original GitHub issueDescription
We have multiple developers working on the same repository and we see that paket.restore.targets is changing a lot of the time.
We assume that different versions of paket are used by different developers which causing the paket.restore.targets file to be updated/downgraded when different developers work on the repo. Even with paket “magic mode” there may be some delays as to when one developer gets an update and when another developer does.
If we could have the version number of paket to which the paket.restore.targets file belongs inside the file then developers can see whether they are behind on a paket version.
This would also open up the possibility to only update the paket.restore.targets when the version is newer and maybe warn that you are using an older version of paket.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Imho the solution ist to force the team to use same paket version. Just put “version x.yyy.z” on top of the dependencies file
One thing I don’t remember is if the non-magic bootstrapper check the version and re-downloads if it finds a
paket.exe(I didn’t change it in anyway)If I might ask, why not magic mode ?