title: Couldn't find package "my-custom-package" on the "npm" registry
body: <p>I have a Node.js project separated in several custom packages, each having their own <code>package.json</code> file. This is all custom code for that specific project. Some have <code>dependencies/devDependencies</code>, and when running</p>
  
  <pre><code>yarn install
  </code></pre>
  
  <p>all dependencies are installed and everything goes smoothly.</p>
  
  <p>The content of the package.json files are as follows:</p>
  
  <pre><code>{
    "name": "my-custom-package-name", // This changes in each package.json file
    "version": "1.0.3-beta.1", // The version is the same in all package.json files
    "private": true,
    "repository": "https://github.com/my-organization/my-private-repo",
    [...]
  }
  </code></pre>
  
  <p>Now I am asked to do a new deployment of the project to production and to increment the version number of the packages for the new release. So I change the version number in each <code>package.json</code> file by removing the prerelease tag to:</p>
  
  <pre><code>"version": "1.0.3.1"
  </code></pre>
  
  <p>But then, if I run <code>yarn install</code> again, for each package where the prerelease tag was removed from the version number of the custom package, I get an error like this:</p>
  
  <pre><code>yarn install v1.3.2
  [1/4] Resolving packages...
  error Couldn't find package "my-custom-package-name" on the "npm" registry.
  info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
  </code></pre>
  
  <p>Why is this happening when the prerelease tag is removed?
  Why is this not happening when the prerelease tag is there?</p>
  
  <p>Those packages are not being used as dependencies for any other package of the project, so why is yarn trying to resolve a package on npm that matches the name and version of the package.json files?</p>
  
  <p>I really looked around on the Web trying to find answers relating to this, but could not find anything relevant.</p>