Do you want to request a _feature_ or report a _bug_?
_bug_
What is the current behavior?
Doesn't re-fetch git repo if branch revision has changed.
If the current behavior is a bug, please provide the steps to reproduce.
"mydep": "github:myrepo/mydep#mybranch"
"mydep2": "github:myrepo/mydep2"
yarn upgrade
yarn
What is the expected behavior?
Check if the correct revision is local and otherwise fetch the latest
Please mention your node.js, yarn and operating system version.
OSX Sierra
yarn 15.1
Possibly related to #1017.
I'm seeing this even when using hashes of commits, and explicitly updating package.json to a newer hash.
E.g., first yarn install with:
"dependencies": {
"module": "user/module#deadbeef"
}
Then update to:
"dependencies": {
"module": "user/module#badf00d"
}
yarn install again. yarn.lock will say that it's now at badf00d, but the installed version will still be deadbeef.
If you force reinstallation with yarn cache clean && rm -rf node_modules && yarn install, then the correct version will be installed.
I was hoping that this might have been fixed by #1641, but I tested yarn 0.17.3 and the bug still occurs.
Should be fixed now #2074
I get the same issue on OSX High Sierra v10.13.4, yarn 1.6.0
i am still getting this issue on v1.17.3. yarn cache clean && rm -rf node_modules && yarn install did not work
same issue on v1.22.4
Most helpful comment
I get the same issue on OSX High Sierra v10.13.4, yarn 1.6.0