[Bug] Cannot migrate legacy lockfiles with private GitHub Package dependencies

Describe the bug

In legacy lockfiles private GitHub Package dependencies resolved value has the following pattern: https://npm.pkg.github.com/download/@account/project/1.0.0/someverylong#hashvalue. Attempting to migrate to yarn@berry results with the Only some patterns can be imported from legacy lockfiles error. That’s because there is no .git or .tar.gz or .tgz in there.

Environment:

• OSX
• Node version 12.14.1
• Yarn version 2.0.0-rc.27

[yarnbot]

Hi! 👋

This issue looks stale, and doesn’t feature the reproducible label - which implies that you didn’t provide a working reproduction using Sherlock. As a result, it’ll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we’re a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolution faster). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it’s a Windows-only issue), a maintainer will have to manually add the upholded label.

[DimitrK]

Same here although mine has a .tgz in there yet is served through an artifacts repository

➤ YN0014: │ webpack-hot-middleware@npm:^2.25.0: Only some patterns can be imported from legacy lockfiles (not "https://mycompany.artifactory.com/mycompany/api/npm/npm/webpack-hot-middleware/-/webpack-hot-middleware-2.25.0.tgz#4528a0a63ec37f8f8ef565cf9e534d57d09fe706")