dependabot[bot] opened a new pull request, #155: URL: https://github.com/apache/echarts-handbook/pull/155
Bumps [tar](https://github.com/isaacs/node-tar) to 7.5.7 and updates ancestor dependency [nuxt](https://github.com/nuxt/nuxt/tree/HEAD/packages/nuxt). These dependencies need to be updated together. Updates `tar` from 6.2.1 to 7.5.7 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md";>tar's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <h2>7.5</h2> <ul> <li>Added <code>zstd</code> compression support.</li> <li>Consistent TOCTOU behavior in sync t.list</li> <li>Only read from ustar block if not specified in Pax</li> <li>Fix sync tar.list when file size reduces while reading</li> <li>Sanitize absolute linkpaths properly</li> <li>Prevent writing hardlink entries to the archive ahead of their file target</li> </ul> <h2>7.4</h2> <ul> <li>Deprecate <code>onentry</code> in favor of <code>onReadEntry</code> for clarity.</li> </ul> <h2>7.3</h2> <ul> <li>Add <code>onWriteEntry</code> option</li> </ul> <h2>7.2</h2> <ul> <li>DRY the command definitions into a single <code>makeCommand</code> method, and update the type signatures to more appropriately infer the return type from the options and arguments provided.</li> </ul> <h2>7.1</h2> <ul> <li>Update minipass to v7.1.0</li> <li>Update the type definitions of <code>write()</code> and <code>end()</code> methods on <code>Unpack</code> and <code>Parser</code> classes to be compatible with the NodeJS.WritableStream type in the latest versions of <code>@types/node</code>.</li> </ul> <h2>7.0</h2> <ul> <li>Drop support for node <18</li> <li>Rewrite in TypeScript, provide ESM and CommonJS hybrid interface</li> <li>Add tree-shake friendly exports, like <code>import('tar/create')</code> and <code>import('tar/read-entry')</code> to get individual functions or classes.</li> <li>Add <code>chmod</code> option that defaults to false, and deprecate <code>noChmod</code>. That is, reverse the default option regarding explicitly setting file system modes to match tar entry settings.</li> <li>Add <code>processUmask</code> option to avoid having to call <code>process.umask()</code> when <code>chmod: true</code> (or <code>noChmod: false</code>) is set.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/isaacs/node-tar/commit/4a37eb9a1cf1137df4eb70c5c7f849f412ff3cdb";><code>4a37eb9</code></a> 7.5.7</li> <li><a href="https://github.com/isaacs/node-tar/commit/f4a7aa9bc3d717c987fdf1480ff7a64e87ffdb46";><code>f4a7aa9</code></a> fix: properly sanitize hard links containing ..</li> <li><a href="https://github.com/isaacs/node-tar/commit/394ece6ad8d81742a4e4058af227c616cd947a25";><code>394ece6</code></a> 7.5.6</li> <li><a href="https://github.com/isaacs/node-tar/commit/7d4cc17c76f6bd11dcd83de47187dc6dff206eee";><code>7d4cc17</code></a> fix race puting a Link ahead of its target File</li> <li><a href="https://github.com/isaacs/node-tar/commit/26ab90474e642cf00d84a05bcdc2eaf2a19f1581";><code>26ab904</code></a> 7.5.5</li> <li><a href="https://github.com/isaacs/node-tar/commit/e9a1ddb821b29ddee75b9470dd511066148c8070";><code>e9a1ddb</code></a> fix: do not prevent valid linkpaths within archive</li> <li><a href="https://github.com/isaacs/node-tar/commit/911c886bb170a6ee3db05fd3709221752213ec8a";><code>911c886</code></a> 7.5.4</li> <li><a href="https://github.com/isaacs/node-tar/commit/3b1abfae650056edfabcbe0a0df5954d390521e6";><code>3b1abfa</code></a> normalize out unicode ligatures</li> <li><a href="https://github.com/isaacs/node-tar/commit/a43478c5c51a71ec996cea62ff824eb9dc9dd17c";><code>a43478c</code></a> remove some unused files</li> <li><a href="https://github.com/isaacs/node-tar/commit/970c58f6d3d0c932081f8b40218f612db2fabb5a";><code>970c58f</code></a> update deps</li> <li>Additional commits viewable in <a href="https://github.com/isaacs/node-tar/compare/v6.2.1...v7.5.7";>compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~isaacs";>isaacs</a>, a new releaser for tar since your current version.</p> </details> <br /> Updates `nuxt` from 2.15.8 to 4.3.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/nuxt/nuxt/releases";>nuxt's releases</a>.</em></p> <blockquote> <h2>v4.3.0</h2> <blockquote> <p>4.3.0 is the next minor release.</p> </blockquote> <p>Nuxt 4.3 brings powerful new features for layouts, caching, and developer experience – plus significant performance improvements under the hood.</p> <h2>📣 Some News</h2> <h3>Extended v3 Support</h3> <p>Early this month, I <a href="https://github.com/nuxt/nuxt/discussions/33918";>opened a discussion</a> to find out how the upgrade had gone from v3 to v4. I was really pleased to hear how well it had gone for most people.</p> <p>Having said that, we're committed to making sure no one gets left behind. And so we will <strong>continue to provide security updates and critical bug fix releases</strong> beyond the previously announced end-of-life date of January 31, 2026, meaning Nuxt v3 will meet its end-of-life on July 31, 2026.</p> <blockquote> <p>[!TIP] As usual, today also brings a minor release for v3, with many of the same improvements backported from v4.3.</p> </blockquote> <h3>Preparing for Nuxt 5</h3> <p>We're closer than ever to the releases of Nuxt v5 and Nitro v3. In the coming weeks, the <code>main</code> branch of the Nuxt repository will begin receiving initial commits for Nuxt 5. However, it's still <strong>business as usual</strong>.</p> <ul> <li>Continue making pull requests to the <code>main</code> branch</li> <li>We'll backport changes to the <code>4.x</code> and <code>3.x</code> branches</li> </ul> <p>Keep an eye out on the <a href="https://nuxt.com/docs/4.x/getting-started/upgrade";>Upgrade Guide</a> – we'll be adding details about how you can already start migrating your projects to prepare for Nuxt v4 with <code>future.compatibilityVersion: 5</code>.</p> <h2>🗂️ Route Rule Layouts</h2> <p>But that's enough about the future. We have a lot of good things for you today!</p> <p>First, you can now set layouts directly in route rules using the new <code>appLayout</code> property (<a href="https://redirect.github.com/nuxt/nuxt/pull/31092";>#31092</a>). This provides a centralized, declarative way to manage layouts across your application without scattering <code>definePageMeta</code> calls throughout your pages.</p> <pre lang="ts" data-meta="[nuxt.config.ts]"><code>export default defineNuxtConfig({ routeRules: { '/admin/**': { appLayout: 'admin' }, '/dashboard/**': { appLayout: 'dashboard' }, '/auth/**': { appLayout: 'minimal' } } }) </code></pre> <p>This might be useful for:</p> <ul> <li>Admin panels with a shared layout across many routes</li> <li>Marketing pages that need a different layout from the app</li> </ul> <blockquote> <p>[!TIP] Plus, you can pass props to layouts now! See <a href="https://github.com/nuxt/nuxt/tree/HEAD/packages/nuxt/blob/HEAD/#layout-props-with-setpagelayout";>the <code>setPageLayout</code> improvements below</a>.</p> </blockquote> <h2>📦 ISR/SWR Payload Extraction</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/nuxt/nuxt/commit/b5bd7d9195bbd1c9cb174d43f6da2912fbd40bd3";><code>b5bd7d9</code></a> v4.3.0</li> <li><a href="https://github.com/nuxt/nuxt/commit/fd7a4b04993a699f1db7215b8dc459899d45ddfc";><code>fd7a4b0</code></a> fix(nuxt): ensure we inline styles for <code>hydrate-never</code> components (<a href="https://github.com/nuxt/nuxt/tree/HEAD/packages/nuxt/issues/34132";>#34132</a>)</li> <li><a href="https://github.com/nuxt/nuxt/commit/2723020e6281c962f803ff4ff96b7949d694cfa4";><code>2723020</code></a> fix(nuxt): add <code>typeFrom</code> support for <code>imports.d.ts</code> template exports (<a href="https://github.com/nuxt/nuxt/tree/HEAD/packages/nuxt/issues/34135";>#34135</a>)</li> <li><a href="https://github.com/nuxt/nuxt/commit/8d4f9ba5c106e0deb281821bd6058e66595abf37";><code>8d4f9ba</code></a> fix(nuxt): force flush <code>useAsyncData</code> debounced execute post watcher flush (#...</li> <li><a href="https://github.com/nuxt/nuxt/commit/567a1c6fb9ddb0208c4db9d5b13db88e196a9a90";><code>567a1c6</code></a> fix(nuxt): validate placeholder/fallback tags + warn about placeholder/fallba...</li> <li><a href="https://github.com/nuxt/nuxt/commit/f136022cc79eb984bc88484bf5ff0c2781514397";><code>f136022</code></a> chore(deps): update all non-major dependencies (main) (<a href="https://github.com/nuxt/nuxt/tree/HEAD/packages/nuxt/issues/34110";>#34110</a>)</li> <li><a href="https://github.com/nuxt/nuxt/commit/888f0f44f7502d6b5f7546eb12929975e2aab093";><code>888f0f4</code></a> fix(nuxt): add documentation link to server builder error message (<a href="https://github.com/nuxt/nuxt/tree/HEAD/packages/nuxt/issues/34122";>#34122</a>)</li> <li><a href="https://github.com/nuxt/nuxt/commit/d19f1a83eb21994e4401287c83678075208b9297";><code>d19f1a8</code></a> fix(nuxt): force remount suspense when navigating after pending (<a href="https://github.com/nuxt/nuxt/tree/HEAD/packages/nuxt/issues/33991";>#33991</a>)</li> <li><a href="https://github.com/nuxt/nuxt/commit/f3d5bc5f520188f136340ae65af6baf56d34660b";><code>f3d5bc5</code></a> fix(nuxt): decode client-side pathname for non-ASCII route aliases (<a href="https://github.com/nuxt/nuxt/tree/HEAD/packages/nuxt/issues/34043";>#34043</a>)</li> <li><a href="https://github.com/nuxt/nuxt/commit/37763a5549bdf84c8b051cb2ca0a69d771a0fd66";><code>37763a5</code></a> fix(nuxt): rerender <code>NuxtPage</code> when nested <code>NuxtLayout</code> has explicitly disabl...</li> <li>Additional commits viewable in <a href="https://github.com/nuxt/nuxt/commits/v4.3.0/packages/nuxt";>compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by [GitHub Actions](<a href="https://www.npmjs.com/~GitHub";>https://www.npmjs.com/~GitHub</a> Actions), a new releaser for nuxt since your current version.</p> </details> <br /> 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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/echarts-handbook/network/alerts). </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
