<h3 dir="auto">Is there an existing issue for this?</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have searched the existing issues</li>
</ul>
<h3 dir="auto">Current Behavior</h3>
<p dir="auto">Hi there!<br>
I going to migrate my monorepo from lerna to npm 7 and faced with the next issue:<br>
when I doing npm --workspaces version pach - my packages updated as expected, but dependency in "package-a" still have old dependency version of "package-b"</p>
<p dir="auto">how can i solve this issue?</p>
<h3 dir="auto">Is there an existing issue for this?</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have searched the existing issues</li>
</ul>
<h3 dir="auto">Current Behavior</h3>
<p dir="auto">The <code class="notranslate">npm --no-git-tag-version --workspaces version &lt;version&gt;</code> command doesn't update package devDependencies or dependencies with the new version. I'd expect that workspace dependencies would be updated to match the new versions that were set.</p>
<h3 dir="auto">Expected Behavior</h3>
<p dir="auto">npm --no-git-tag-version --workspaces version "2.0.0-alpha1" should update all workspace package versions (currently does) and also update the package dependency versions</p>
<h3 dir="auto">Steps To Reproduce</h3>
<ol dir="auto">
<li>Setup a new npm workspace</li>
<li>Create <code class="notranslate">/packages/packagea</code> :</li>
</ol>
<div class="highlight highlight-source-json notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="{
  &quot;name&quot;: &quot;packagea&quot;,
  &quot;version&quot;: &quot;2.0.0-dev&quot;
}"><pre class="notranslate">{
  <span class="pl-ent">"name"</span>: <span class="pl-s"><span class="pl-pds">"</span>packagea<span class="pl-pds">"</span></span>,
  <span class="pl-ent">"version"</span>: <span class="pl-s"><span class="pl-pds">"</span>2.0.0-dev<span class="pl-pds">"</span></span>
}</pre></div>
<ol start="3" dir="auto">
<li>Create ``/packages/packageb`:</li>
</ol>
<div class="highlight highlight-source-json notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="{
  &quot;name&quot;: &quot;packageb&quot;,
  &quot;version&quot;: &quot;2.0.0-dev&quot;,
  &quot;dependencies&quot;: {
      &quot;packagea&quot;: &quot;2.0.0-dev&quot;
    }
}"><pre class="notranslate">{
  <span class="pl-ent">"name"</span>: <span class="pl-s"><span class="pl-pds">"</span>packageb<span class="pl-pds">"</span></span>,
  <span class="pl-ent">"version"</span>: <span class="pl-s"><span class="pl-pds">"</span>2.0.0-dev<span class="pl-pds">"</span></span>,
  <span class="pl-ent">"dependencies"</span>: {
      <span class="pl-ent">"packagea"</span>: <span class="pl-s"><span class="pl-pds">"</span>2.0.0-dev<span class="pl-pds">"</span></span>
    }
}</pre></div>
<ol start="3" dir="auto">
<li>Run <code class="notranslate">npm --no-git-tag-version --workspaces version "2.0.0-alpha1"</code></li>
<li>notice the package versions are updated but the dependencies are not.</li>
</ol>
<p dir="auto">I have an existing setup located here: <a href="https://github.com/exceptionless/Exceptionless.JavaScript/tree/feature/workspaces">https://github.com/exceptionless/Exceptionless.JavaScript/tree/feature/workspaces</a> that reproduces it (but package names are changed...)</p>
<p dir="auto">I noticed this after getting the following error:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="npm ERR! code ETARGET
npm ERR! notarget No matching version found for @exceptionless/core@2.0.0-dev.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist."><pre lang="npm" class="notranslate"><code class="notranslate">npm ERR! code ETARGET
npm ERR! notarget No matching version found for @exceptionless/core@2.0.0-dev.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
</code></pre></div>
<h3 dir="auto">Environment</h3>
<ul dir="auto">
<li>OS:  Windows 10 latest</li>
<li>Node: v16.1.0</li>
<li>npm:  7.17.0</li>
</ul>