build(deps-dev): bump npm-check-updates from 16.14.20 to 17.0.6#17

Bumps [npm-check-updates](https://github.com/raineorshine/npm-check-updates) from 16.14.20 to 17.0.6. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/releases">npm-check-updates's releases</a>.</em></p> <blockquote> <h2>v17.0.0</h2> <h3>Breaking</h3> <ul> <li>Require node &gt;= 18.18.0</li> <li>In workspaces mode, <code>--root</code> is now set by default (<a href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1353">#1353</a>) <ul> <li>To <strong>not</strong> check the root package.json, use <code>--no-root</code>.</li> </ul> </li> <li>If you have a <a href="https://nodejs.org/api/packages.html#packagemanager">packageManager</a> field in your package.json, it is now upgraded by default (<a href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1390">#1390</a>) <ul> <li>Use <code>--dep prod,dev,optional</code> for the old behavior.</li> </ul> </li> </ul> <h2>v17.0.0-1</h2> <p>This is the first prerelease in preparation for the next major v17. It mainly involves a node engines bump and lot of internal dependency upgrades, <strong>so if you notice any regressions, please let me know!</strong></p> <p>Run <code>npx [email protected]</code> to test.</p> <p>There are a two more breaking/high-risk changes I intend to make for the v17 release, which I will also release as prerelease versions for testing.</p> <p>Thanks for your help and enjoy! 🍰</p> <h3>Breaking</h3> <ul> <li>[x] Require node &gt;= 18.18.0</li> <li>[x] In workspaces mode, <code>--root</code> is now set by default (<a href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1353">#1353</a>) <ul> <li>To <strong>not</strong> check the root package.json, use <code>--no-root</code>.</li> </ul> </li> <li>[ ] Convert from CommonJS to ESM (<a href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1358">#1358</a>)</li> <li>[ ] Replace pacote with npm-registry-fetch (<a href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1329">#1329</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/eae46923f67ed27441980c1d513ced1f03b7d2cd"><code>eae4692</code></a> 17.0.6</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/369bbdfc19d3a5754c275759c922b38e60c7cba0"><code>369bbdf</code></a> fix: check if upgrade ignored due to engines fails due to usage of ranges (<a href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1">#1</a>...</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/1aec29a7d9901e4365154f2a6c0219bee2c2f497"><code>1aec29a</code></a> 17.0.5</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/71423af035a3548f39817c3a4a430c17bfc28f54"><code>71423af</code></a> fix: fetchPartialPackument fallback is not done right (<a href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1446">#1446</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/cf94481f74f6dae40f424b26d68eb4203cda3588"><code>cf94481</code></a> 17.0.4</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/76d7d34898333d25a11f296fff82ef1ed4db3cd2"><code>76d7d34</code></a> fix: yarn is not pasing yarn config to getEngines (<a href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1445">#1445</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/ed0767b2d81ee1cb62d600b53141d00019127ea2"><code>ed0767b</code></a> CHANGELOG</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/888e222d05fa0d960ea317232c128af3a96a8d73"><code>888e222</code></a> 17.0.3</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/c226e38f599c1fd0abd30ae98b2139b8e628e739"><code>c226e38</code></a> Allow custom registries without trailing slash (<a href="https://redirect.github.com/raineorshine/npm-check-updates/issues/1440">#1440</a>)</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/1dfe89dcd91431067e00d539fc68f3d72892c6b2"><code>1dfe89d</code></a> 17.0.2</li> <li>Additional commits viewable in <a href="https://github.com/raineorshine/npm-check-updates/compare/v16.14.20...v17.0.6">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>