Install from a branch gets cached

[HommeSauvage]

Do you want to request a feature or report a bug?
bug

What is the current behavior?
Yarn is getting the same package from cache when using a branch even if the branch has new commits. Event after running npm install <package> and getting the new package, running yarn after will bring back the old cached package.

If the current behavior is a bug, please provide the steps to reproduce.
Try installing a branch from a repository:
"<package>": "git+ssh://[email protected]/<user>/<package>.git#<branch>",
yarn, add new commits to <branch>, then yarn again. You will get a cached version without the new commits.

What is the expected behavior?
Since we are not specifying a version in dependencies but a branch, yarn should get the latest commit from the branch. npm works well.

Please mention your node.js, yarn and operating system version.
Node 7.2.1, yarn 0.17.10, macOS Sierra.

[bestander]

Should be fixed now #2074.
Please reopen if the issue is still there

[Dmitra]

can reproduce on node 8.3.0 yarn 0.27.5 Ubuntu 16.04

[BYK]

@Dmitra please try a more recent version. You can try 0.28.1 from NPM or the nightlies.

[Dmitra]

@BYK can't reproduce on yarn 1.0.0-20170809.1554

[BYK]

@Dmitra that means it is fixed on master, yay! And thanks :)

[xomaczar]

[email protected] exhibits similar behavior.

[email protected]
[email protected]

[xomaczar]

Same thing in [email protected]. The only way to force fetching is with yarn upgrade <package-name>

[askielboe]

Having the same issue. Have to run yarn upgrade after every yarn install to get the upgraded packages.

yarn install always picks some random old version. :(

[valoricDe]

I vote for reopening this issue.

[xomaczar]

Yes same here, this can cause an incorrect release being bundled in our production code...

[xomaczar]

cc @bestander

[bestander]

@xomaczar, could you open a new issue with a repro step please?

[askielboe]

I've created a new issue with steps to reproduce: #4734