wrapper/tailwindcss
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions
tailwindcss/playgrounds/v3/package.json

27 lines
582 B
JSON
Raw Permalink Normal View History

Register `migrateImport` to ensure it actually runs (#14769) This PR makes sure the `migrateImport` codemod is properly registered so that it runs as part of the upgrade process. ## Test plan This PR adds a new `v3` playground with an `upgrade` script that you can use to run the upgrade from the local package. When you add a non-prefixed `@import` to the v3 example, the paths are now properly updated with no errors logged: https://github.com/user-attachments/assets/85949bbb-756b-4ee2-8ac0-234fe1b2ca39 --------- Co-authored-by: Adam Wathan <4323180+adamwathan@users.noreply.github.com> Co-authored-by: Philipp Spiess <hello@philippspiess.com>
2024-10-24 11:00:25 -04:00
{
"name": "v3-playground",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint",
"upgrade": "node scripts/upgrade.mjs"
},
"dependencies": {
🚨 [security] Update all of nextjs 15.4.4 → 15.4.7 (patch) (#18838) <hr> 🚨 <b>Your current dependencies have known security vulnerabilities</b> 🚨 This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible! <hr> Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ eslint-config-next (15.4.4 → 15.4.7) Sorry, we couldn't find anything useful about this release. #### ✳️ next (15.4.4 → 15.4.7) · [Repo](https://github.com/vercel/next.js) <details> <summary>Security Advisories 🚨</summary> <h4><a href="https://bounce.depfu.com/github.com/vercel/next.js/security/advisories/GHSA-xv57-4mr9-wg8v">🚨 Next.js Content Injection Vulnerability for Image Optimization</a></h4> <blockquote><p dir="auto">A vulnerability in <strong>Next.js Image Optimization</strong> has been fixed in <strong>v15.4.5</strong> and <strong>v14.2.31</strong>. The issue allowed attacker-controlled external image sources to trigger file downloads with arbitrary content and filenames under specific configurations. This behavior could be abused for phishing or malicious file delivery.</p> <p dir="auto">All users relying on <code class="notranslate">images.domains</code> or <code class="notranslate">images.remotePatterns</code> are encouraged to upgrade and verify that external image sources are strictly validated.</p> <p dir="auto">More details at <a href="https://vercel.com/changelog/cve-2025-55173">Vercel Changelog</a></p></blockquote> <h4><a href="https://bounce.depfu.com/github.com/vercel/next.js/security/advisories/GHSA-g5qg-72qw-gw5v">🚨 Next.js Affected by Cache Key Confusion for Image Optimization API Routes</a></h4> <blockquote><p dir="auto">A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. When images returned from API routes vary based on request headers (such as <code class="notranslate">Cookie</code> or <code class="notranslate">Authorization</code>), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug.</p> <p dir="auto">All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled.</p> <p dir="auto">More details at <a href="https://vercel.com/changelog/cve-2025-57752">Vercel Changelog</a></p></blockquote> <h4><a href="https://bounce.depfu.com/github.com/vercel/next.js/security/advisories/GHSA-4342-x723-ch2f">🚨 Next.js Improper Middleware Redirect Handling Leads to SSRF</a></h4> <blockquote><p dir="auto">A vulnerability in <strong>Next.js Middleware</strong> has been fixed in <strong>v14.2.32</strong> and <strong>v15.4.7</strong>. The issue occurred when request headers were directly passed into <code class="notranslate">NextResponse.next()</code>. In self-hosted applications, this could allow Server-Side Request Forgery (SSRF) if certain sensitive headers from the incoming request were reflected back into the response.</p> <p dir="auto">All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the <code class="notranslate">next()</code> function.</p> <p dir="auto">More details at <a href="https://vercel.com/changelog/cve-2025-57822">Vercel Changelog</a></p></blockquote> </details> <details> <summary>Release Notes</summary> <h4><a href="https://github.com/vercel/next.js/releases/tag/v15.4.7">15.4.7</a></h4> <blockquote><div class="markdown-alert markdown-alert-note" dir="auto"> <p class="markdown-alert-title" dir="auto"><svg class="octicon octicon-info mr-2" viewbox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path d="M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8Zm8-6.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13ZM6.5 7.75A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75ZM8 6a1 1 0 1 1 0-2 1 1 0 0 1 0 2Z"></path></svg>Note</p> <p dir="auto">This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </div> <h3 dir="auto">Core Changes</h3> <ul dir="auto"> <li>fix router handling when setting a location response header <a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82588">#82588</a> </li> </ul> <h3 dir="auto">Credits</h3> <p dir="auto">Huge thanks to <a href="https://bounce.depfu.com/github.com/ztanner">@ztanner</a> for helping!</p></blockquote> <h4><a href="https://github.com/vercel/next.js/releases/tag/v15.4.6">15.4.6</a></h4> <blockquote><div class="markdown-alert markdown-alert-note" dir="auto"> <p class="markdown-alert-title" dir="auto"><svg class="octicon octicon-info mr-2" viewbox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path d="M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8Zm8-6.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13ZM6.5 7.75A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75ZM8 6a1 1 0 1 1 0-2 1 1 0 0 1 0 2Z"></path></svg>Note</p> <p dir="auto">This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </div> <h3 dir="auto">Core Changes</h3> <ul dir="auto"> <li>fix: <code class="notranslate">_error</code> page's <code class="notranslate">req.url</code> can be overwritten to dynamic param on minimal mode (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82347">#82347</a>)</li> <li>fix: add <code class="notranslate">?dpl</code> to fonts in <code class="notranslate">/_next/static/media</code> (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82384">#82384</a>)</li> </ul> <h3 dir="auto">Credits</h3> <p dir="auto">Huge thanks to <a href="https://bounce.depfu.com/github.com/devjiwonchoi">@devjiwonchoi</a>, <a href="https://bounce.depfu.com/github.com/ijjk">@ijjk</a>, and <a href="https://bounce.depfu.com/github.com/styfle">@styfle</a> for helping!</p></blockquote> <h4><a href="https://github.com/vercel/next.js/releases/tag/v15.4.5">15.4.5</a></h4> <blockquote><div class="markdown-alert markdown-alert-note" dir="auto"> <p class="markdown-alert-title" dir="auto"><svg class="octicon octicon-info mr-2" viewbox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path d="M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8Zm8-6.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13ZM6.5 7.75A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75ZM8 6a1 1 0 1 1 0-2 1 1 0 0 1 0 2Z"></path></svg>Note</p> <p dir="auto">This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </div> <h3 dir="auto">Core Changes</h3> <ul dir="auto"> <li>Fix API stripping JSON incorrectly (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82062">#82062</a>)</li> <li>Fix i18n fallback: false collision (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82158">#82158</a>)</li> <li>Revert "Fix tracing of server actions imported by client components (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82167">#82167</a>)</li> <li>Ensure setAssetPrefix updates config instance (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82165">#82165</a>)</li> <li>Turbopack: update mimalloc (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82166">#82166</a>)</li> <li>fix(next/image): fix image-optimizer.ts headers (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82175">#82175</a>)</li> <li>fix(next/image): improve and simplify detect-content-type (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82174">#82174</a>)</li> </ul> <h3 dir="auto">Credits</h3> <p dir="auto">Huge thanks to <a href="https://bounce.depfu.com/github.com/ijjk">@ijjk</a>, <a href="https://bounce.depfu.com/github.com/sokra">@sokra</a>, and <a href="https://bounce.depfu.com/github.com/styfle">@styfle</a> for helping!</p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/next/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href="https://github.com/vercel/next.js/compare/fe5db65859f0658d1c4701635ec4f4e5ec507e64...f30d815859e932e09222e93bb6e8a376b918d874">See the full diff on Github</a>. The new version differs by 14 commits:</p> <ul> <li><a href="https://github.com/vercel/next.js/commit/f30d815859e932e09222e93bb6e8a376b918d874"><code>v15.4.7</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/1a026e338d2b8c977c8949a134168952338d6d01"><code>fix router handling when setting a location response header (#82588)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/be4aafd4b744fbf6500b311b74c84243f70a3059"><code>v15.4.6</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/91e5b6b84f56c096dc2bb647eb384388e06489fd"><code>Backport &quot;fix: add `?dpl` to fonts in `/_next/static/media` (#82384)&quot; (#82421)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/f1629d939597cc46ccbe44fe66bda91eac31e219"><code>Backport &quot;[Pages] fix: `_error` page&#39;s `req.url` can be overwritten t… (#82377)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/b9aab5dbe926c256d439bfecb226693dcd1a1be4"><code>v15.4.5</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/a8c93c49dd2d42a2ced8a17bc53b3fea11d25c96"><code>Disable test new tests jobs</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/ed2a6c754831406f8cd724eb52a562bb124c1504"><code>[backport]: fix(next/image): improve and simplify detect-content-type (#82118) (#82174)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/f00fcc9011e7d0ef027021fc8424f51b8ac97880"><code>[backport]: fix(next/image): fix image-optimizer.ts headers (#82114) (#82175)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/55a7568e9d12459f8c5f5ae120fe2e228af284bb"><code>Backport: Turbopack: update mimalloc (#81993) (#82166)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/5bc4b368e5bc4d301f94955307e37a0328612408"><code>[backport] Ensure setAssetPrefix updates config instance (#82165)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/717dfb6ec985ba58b20ce6533ceecab213f72c22"><code>[Backport] Revert &quot;Fix tracing of server actions imported by client components (#78968) (#82167)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/6372ba03e85ca598b67fe21daa87dbad328f581b"><code>[backport] Fix i18n fallback: false collision (#82158)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/1e2c3792f88491ab8cfba580b8f17aad17015d17"><code>Fix API stripping JSON incorrectly (#82062)</code></a></li> </ul> </details> --- ![Depfu Status](https://depfu.com/badges/edd6acd35d74c8d41cbb540c30442adf/stats.svg) [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@​depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@​depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@​depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@​depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@​depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@​depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@​depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@​depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@​depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com>
2025-09-01 11:24:56 +02:00
"next": "15.4.7",
Update all of react 19.1.0 → 19.1.1 (patch) (#18669) Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ react (19.1.0 → 19.1.1) · [Repo](https://github.com/facebook/react) · [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/facebook/react/releases/tag/v19.1.1">19.1.1</a></h4> <blockquote><h3 dir="auto">React</h3> <ul dir="auto"> <li>Fixed Owner Stacks to work with ES2015 function.name semantics (<a href="https://bounce.depfu.com/github.com/facebook/react/pull/33680">#33680</a> by <a href="https://bounce.depfu.com/github.com/hoxyq">@hoxyq</a>)</li> </ul></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/react/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href="https://github.com/facebook/react/compare/4a9df08157f001c01b078d259748512211233dcf...02ef49580922f87180f32618b9d1c70b75b968b7">See the full diff on Github</a>. The new version differs by 11 commits:</p> <ul> <li><a href="https://github.com/facebook/react/commit/02ef49580922f87180f32618b9d1c70b75b968b7"><code>Reset packages we are not releasing to currently published versions</code></a></li> <li><a href="https://github.com/facebook/react/commit/3f178f55fc76debfef6883d74b8d3ace2ebe8176"><code>[Release] Update build script to properly set React Native&#39;s renderers version (#33972)</code></a></li> <li><a href="https://github.com/facebook/react/commit/87e33ca2b7c4479342091ae642f01266af7ebec9"><code>Set release versions to 19.1.1</code></a></li> <li><a href="https://github.com/facebook/react/commit/52cf381c722bb8171c06d8c7aa0bf057d0668c39"><code>[eprh] Bump stable version (#32978)</code></a></li> <li><a href="https://github.com/facebook/react/commit/b793948e15ff714fadea026dcaef9385dce14a19"><code>Bump next prerelease version numbers (#32782)</code></a></li> <li><a href="https://github.com/facebook/react/commit/73e4ba42cd9bb1e49de7f4d24298b0e99b78897d"><code>Allow runtime_build_and_test action to trigger manually (#33796)</code></a></li> <li><a href="https://github.com/facebook/react/commit/5a1eb6f61a10cd007f1d372a2710d4e0224f4a79"><code>fix: rename bottom stack frame (#33680)</code></a></li> <li><a href="https://github.com/facebook/react/commit/01eae200bf6755e49770bc947d6aaf5ef2d2e980"><code>[DevTools] Get source location from structured callsites in prepareStackTrace (#33143)</code></a></li> <li><a href="https://github.com/facebook/react/commit/0e6781a06b24a3228eed056dc683984880e53da9"><code>Enable the `enableEagerAlternateStateNodeCleanup` Feature Flag (#33447)</code></a></li> <li><a href="https://github.com/facebook/react/commit/2cd3c424ea9637cb15858db4353b5a71e9b505c6"><code>Add eager alternate.stateNode cleanup (#33161)</code></a></li> <li><a href="https://github.com/facebook/react/commit/a24654e65b7664686a47d281fae0feb1de1dbe59"><code>Ship enableFabricCompleteRootInCommitPhase (#33064)</code></a></li> </ul> </details> #### ✳️ react-dom (19.1.0 → 19.1.1) · [Repo](https://github.com/facebook/react) · [Changelog](https://github.com/facebook/react/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/facebook/react/releases/tag/v19.1.1">19.1.1</a></h4> <blockquote><h3 dir="auto">React</h3> <ul dir="auto"> <li>Fixed Owner Stacks to work with ES2015 function.name semantics (<a href="https://bounce.depfu.com/github.com/facebook/react/pull/33680">#33680</a> by <a href="https://bounce.depfu.com/github.com/hoxyq">@hoxyq</a>)</li> </ul></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/react-dom/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href="https://github.com/facebook/react/compare/4a9df08157f001c01b078d259748512211233dcf...02ef49580922f87180f32618b9d1c70b75b968b7">See the full diff on Github</a>. The new version differs by 11 commits:</p> <ul> <li><a href="https://github.com/facebook/react/commit/02ef49580922f87180f32618b9d1c70b75b968b7"><code>Reset packages we are not releasing to currently published versions</code></a></li> <li><a href="https://github.com/facebook/react/commit/3f178f55fc76debfef6883d74b8d3ace2ebe8176"><code>[Release] Update build script to properly set React Native&#39;s renderers version (#33972)</code></a></li> <li><a href="https://github.com/facebook/react/commit/87e33ca2b7c4479342091ae642f01266af7ebec9"><code>Set release versions to 19.1.1</code></a></li> <li><a href="https://github.com/facebook/react/commit/52cf381c722bb8171c06d8c7aa0bf057d0668c39"><code>[eprh] Bump stable version (#32978)</code></a></li> <li><a href="https://github.com/facebook/react/commit/b793948e15ff714fadea026dcaef9385dce14a19"><code>Bump next prerelease version numbers (#32782)</code></a></li> <li><a href="https://github.com/facebook/react/commit/73e4ba42cd9bb1e49de7f4d24298b0e99b78897d"><code>Allow runtime_build_and_test action to trigger manually (#33796)</code></a></li> <li><a href="https://github.com/facebook/react/commit/5a1eb6f61a10cd007f1d372a2710d4e0224f4a79"><code>fix: rename bottom stack frame (#33680)</code></a></li> <li><a href="https://github.com/facebook/react/commit/01eae200bf6755e49770bc947d6aaf5ef2d2e980"><code>[DevTools] Get source location from structured callsites in prepareStackTrace (#33143)</code></a></li> <li><a href="https://github.com/facebook/react/commit/0e6781a06b24a3228eed056dc683984880e53da9"><code>Enable the `enableEagerAlternateStateNodeCleanup` Feature Flag (#33447)</code></a></li> <li><a href="https://github.com/facebook/react/commit/2cd3c424ea9637cb15858db4353b5a71e9b505c6"><code>Add eager alternate.stateNode cleanup (#33161)</code></a></li> <li><a href="https://github.com/facebook/react/commit/a24654e65b7664686a47d281fae0feb1de1dbe59"><code>Ship enableFabricCompleteRootInCommitPhase (#33064)</code></a></li> </ul> </details> --- ![Depfu Status](https://depfu.com/badges/edd6acd35d74c8d41cbb540c30442adf/stats.svg) [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@​depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@​depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@​depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@​depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@​depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@​depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@​depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@​depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@​depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> Co-authored-by: Jordan Pittman <jordan@cryptica.me>
2025-08-12 13:59:07 +00:00
"react": "^19.1.1",
"react-dom": "^19.1.1",
Register `migrateImport` to ensure it actually runs (#14769) This PR makes sure the `migrateImport` codemod is properly registered so that it runs as part of the upgrade process. ## Test plan This PR adds a new `v3` playground with an `upgrade` script that you can use to run the upgrade from the local package. When you add a non-prefixed `@import` to the v3 example, the paths are now properly updated with no errors logged: https://github.com/user-attachments/assets/85949bbb-756b-4ee2-8ac0-234fe1b2ca39 --------- Co-authored-by: Adam Wathan <4323180+adamwathan@users.noreply.github.com> Co-authored-by: Philipp Spiess <hello@philippspiess.com>
2024-10-24 11:00:25 -04:00
"tailwindcss": "^3"
},
"devDependencies": {
"@types/node": "^20.14.8",
Update @types/react 19.1.8 → 19.1.9 (patch) (#18673) Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @​types/react (19.1.8 → 19.1.9) · [Repo](https://github.com/DefinitelyTyped/DefinitelyTyped) Sorry, we couldn't find anything useful about this release. --- ![Depfu Status](https://depfu.com/badges/edd6acd35d74c8d41cbb540c30442adf/stats.svg) [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@​depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@​depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@​depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@​depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@​depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@​depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@​depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@​depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@​depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com>
2025-08-11 14:17:07 +00:00
"@types/react": "^19.1.9",
Update @types/react-dom 19.1.6 → 19.1.7 (patch) (#18674) Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ @​types/react-dom (19.1.6 → 19.1.7) · [Repo](https://github.com/DefinitelyTyped/DefinitelyTyped) Sorry, we couldn't find anything useful about this release. --- ![Depfu Status](https://depfu.com/badges/edd6acd35d74c8d41cbb540c30442adf/stats.svg) [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@​depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@​depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@​depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@​depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@​depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@​depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@​depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@​depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@​depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com>
2025-08-11 10:02:48 -04:00
"@types/react-dom": "^19.1.7",
Update autoprefixer 10.4.20 → 10.4.21 (patch) (#17229)
2025-03-17 09:59:18 +00:00
"autoprefixer": "^10.4.21",
Update eslint 9.32.0 → 9.33.0 (minor) (#18779) Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ eslint (9.32.0 → 9.33.0) · [Repo](https://github.com/eslint/eslint) · [Changelog](https://github.com/eslint/eslint/blob/main/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/eslint/eslint/releases/tag/v9.33.0">9.33.0</a></h4> <blockquote><h2 dir="auto">Features</h2> <ul dir="auto"> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/e07820e66fd1fceaf2620dc931154955a706cc0f"><code class="notranslate">e07820e</code></a> feat: add global object access detection to no-restricted-globals (<a href="https://bounce.depfu.com/github.com/eslint/eslint/pull/19939">#19939</a>) (sethamus)</li> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/90b050ec11557cab08b6be9f05fabf97dba6a63d"><code class="notranslate">90b050e</code></a> feat: support explicit resource management in <code class="notranslate">one-var</code> (<a href="https://bounce.depfu.com/github.com/eslint/eslint/pull/19941">#19941</a>) (Sweta Tanwar)</li> </ul> <h2 dir="auto">Bug Fixes</h2> <ul dir="auto"> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/732433c4fb023f45154b825cdc8cdaf1979d4336"><code class="notranslate">732433c</code></a> fix: allow any type for <code class="notranslate">meta.docs.recommended</code> in custom rules (<a href="https://bounce.depfu.com/github.com/eslint/eslint/pull/19995">#19995</a>) (Francesco Trotta)</li> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/e8a6914a249d036e12494004e586b2a2b6e104d1"><code class="notranslate">e8a6914</code></a> fix: Fixed potential bug in check-emfile-handling.js (<a href="https://bounce.depfu.com/github.com/eslint/eslint/pull/19975">#19975</a>) (諏訪原慶斗)</li> </ul> <h2 dir="auto">Documentation</h2> <ul dir="auto"> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/34f0723e2d0faf8ac8dc95ec56e6d181bd6b67f2"><code class="notranslate">34f0723</code></a> docs: playground button for TypeScript code example (<a href="https://bounce.depfu.com/github.com/eslint/eslint/pull/19671">#19671</a>) (Tanuj Kanti)</li> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/dc942a47daf41228d69072c52f1be20789426862"><code class="notranslate">dc942a4</code></a> docs: Update README (GitHub Actions Bot)</li> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/5a4b6f74320b72f9b6ad8b30f5c463b2b71315af"><code class="notranslate">5a4b6f7</code></a> docs: Update no-multi-assign.md (<a href="https://bounce.depfu.com/github.com/eslint/eslint/pull/19979">#19979</a>) (Yuki Takada (Yukinosuke Takada))</li> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/247e15698e34919a0cd411842fb3e14ac7a8f1ba"><code class="notranslate">247e156</code></a> docs: add missing let declarations in <code class="notranslate">no-plusplus</code> (<a href="https://bounce.depfu.com/github.com/eslint/eslint/pull/19980">#19980</a>) (Yuki Takada (Yukinosuke Takada))</li> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/0d17242b3c25c2ddf8363f4560641acd1ae82ca9"><code class="notranslate">0d17242</code></a> docs: Update README (GitHub Actions Bot)</li> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/fa20b9db8ff90ea9f0527118114dda17c656d095"><code class="notranslate">fa20b9d</code></a> docs: Clarify when to open an issue for a PR (<a href="https://bounce.depfu.com/github.com/eslint/eslint/pull/19974">#19974</a>) (Nicholas C. Zakas)</li> </ul> <h2 dir="auto">Build Related</h2> <ul dir="auto"> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/27fa86551bd173387e29a139293de78b0e14f0f3"><code class="notranslate">27fa865</code></a> build: use <code class="notranslate">ESLint</code> class to generate formatter examples (<a href="https://bounce.depfu.com/github.com/eslint/eslint/pull/19972">#19972</a>) (Milos Djermanovic)</li> </ul> <h2 dir="auto">Chores</h2> <ul dir="auto"> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/425804602ecb9ee5f54d1c38a473cf20538420c5"><code class="notranslate">4258046</code></a> chore: update dependency @eslint/js to v9.33.0 (<a href="https://bounce.depfu.com/github.com/eslint/eslint/pull/19998">#19998</a>) (renovate[bot])</li> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/ad283717ed4764a171120ca7c6cba82a78fa024c"><code class="notranslate">ad28371</code></a> chore: package.json update for @eslint/js release (Jenkins)</li> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/06a22f154c08ea044b3172b357b226d34dfefc6a"><code class="notranslate">06a22f1</code></a> test: resolve flakiness in --mcp flag test (<a href="https://bounce.depfu.com/github.com/eslint/eslint/pull/19993">#19993</a>) (Pixel998)</li> <li> <a href="https://bounce.depfu.com/github.com/eslint/eslint/commit/54920ed229693f23650dace6e567bf44413aaf98"><code class="notranslate">54920ed</code></a> test: switch to <code class="notranslate">Linter.Config</code> in <code class="notranslate">ESLintRules</code> type tests (<a href="https://bounce.depfu.com/github.com/eslint/eslint/pull/19977">#19977</a>) (Francesco Trotta)</li> </ul></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/eslint/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href="https://github.com/eslint/eslint/compare/2364031090daafe34e80904c32065bfe4692d7a2...a90d7c4fe5ef83054e29d21d7ffb442103429d03">See the full diff on Github</a>. The new version differs by 17 commits:</p> <ul> <li><a href="https://github.com/eslint/eslint/commit/a90d7c4fe5ef83054e29d21d7ffb442103429d03"><code>9.33.0</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/9534b55372dbff3bf153384ed2aaab172f998175"><code>Build: changelog update for 9.33.0</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/425804602ecb9ee5f54d1c38a473cf20538420c5"><code>chore: update dependency @eslint/js to v9.33.0 (#19998)</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/ad283717ed4764a171120ca7c6cba82a78fa024c"><code>chore: package.json update for @eslint/js release</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/06a22f154c08ea044b3172b357b226d34dfefc6a"><code>test: resolve flakiness in --mcp flag test (#19993)</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/732433c4fb023f45154b825cdc8cdaf1979d4336"><code>fix: allow any type for `meta.docs.recommended` in custom rules (#19995)</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/34f0723e2d0faf8ac8dc95ec56e6d181bd6b67f2"><code>docs: playground button for TypeScript code example (#19671)</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/dc942a47daf41228d69072c52f1be20789426862"><code>docs: Update README</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/5a4b6f74320b72f9b6ad8b30f5c463b2b71315af"><code>docs: Update no-multi-assign.md (#19979)</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/247e15698e34919a0cd411842fb3e14ac7a8f1ba"><code>docs: add missing let declarations in `no-plusplus` (#19980)</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/0d17242b3c25c2ddf8363f4560641acd1ae82ca9"><code>docs: Update README</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/e07820e66fd1fceaf2620dc931154955a706cc0f"><code>feat: add global object access detection to no-restricted-globals (#19939)</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/fa20b9db8ff90ea9f0527118114dda17c656d095"><code>docs: Clarify when to open an issue for a PR (#19974)</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/54920ed229693f23650dace6e567bf44413aaf98"><code>test: switch to `Linter.Config` in `ESLintRules` type tests (#19977)</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/e8a6914a249d036e12494004e586b2a2b6e104d1"><code>fix: Fixed potential bug in check-emfile-handling.js (#19975)</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/90b050ec11557cab08b6be9f05fabf97dba6a63d"><code>feat: support explicit resource management in `one-var` (#19941)</code></a></li> <li><a href="https://github.com/eslint/eslint/commit/27fa86551bd173387e29a139293de78b0e14f0f3"><code>build: use `ESLint` class to generate formatter examples (#19972)</code></a></li> </ul> </details> --- ![Depfu Status](https://depfu.com/badges/edd6acd35d74c8d41cbb540c30442adf/stats.svg) [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@​depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@​depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@​depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@​depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@​depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@​depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@​depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@​depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@​depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com>
2025-08-22 12:47:01 -04:00
"eslint": "^9.33.0",
🚨 [security] Update all of nextjs 15.4.4 → 15.4.7 (patch) (#18838) <hr> 🚨 <b>Your current dependencies have known security vulnerabilities</b> 🚨 This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible! <hr> Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ eslint-config-next (15.4.4 → 15.4.7) Sorry, we couldn't find anything useful about this release. #### ✳️ next (15.4.4 → 15.4.7) · [Repo](https://github.com/vercel/next.js) <details> <summary>Security Advisories 🚨</summary> <h4><a href="https://bounce.depfu.com/github.com/vercel/next.js/security/advisories/GHSA-xv57-4mr9-wg8v">🚨 Next.js Content Injection Vulnerability for Image Optimization</a></h4> <blockquote><p dir="auto">A vulnerability in <strong>Next.js Image Optimization</strong> has been fixed in <strong>v15.4.5</strong> and <strong>v14.2.31</strong>. The issue allowed attacker-controlled external image sources to trigger file downloads with arbitrary content and filenames under specific configurations. This behavior could be abused for phishing or malicious file delivery.</p> <p dir="auto">All users relying on <code class="notranslate">images.domains</code> or <code class="notranslate">images.remotePatterns</code> are encouraged to upgrade and verify that external image sources are strictly validated.</p> <p dir="auto">More details at <a href="https://vercel.com/changelog/cve-2025-55173">Vercel Changelog</a></p></blockquote> <h4><a href="https://bounce.depfu.com/github.com/vercel/next.js/security/advisories/GHSA-g5qg-72qw-gw5v">🚨 Next.js Affected by Cache Key Confusion for Image Optimization API Routes</a></h4> <blockquote><p dir="auto">A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. When images returned from API routes vary based on request headers (such as <code class="notranslate">Cookie</code> or <code class="notranslate">Authorization</code>), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug.</p> <p dir="auto">All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled.</p> <p dir="auto">More details at <a href="https://vercel.com/changelog/cve-2025-57752">Vercel Changelog</a></p></blockquote> <h4><a href="https://bounce.depfu.com/github.com/vercel/next.js/security/advisories/GHSA-4342-x723-ch2f">🚨 Next.js Improper Middleware Redirect Handling Leads to SSRF</a></h4> <blockquote><p dir="auto">A vulnerability in <strong>Next.js Middleware</strong> has been fixed in <strong>v14.2.32</strong> and <strong>v15.4.7</strong>. The issue occurred when request headers were directly passed into <code class="notranslate">NextResponse.next()</code>. In self-hosted applications, this could allow Server-Side Request Forgery (SSRF) if certain sensitive headers from the incoming request were reflected back into the response.</p> <p dir="auto">All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the <code class="notranslate">next()</code> function.</p> <p dir="auto">More details at <a href="https://vercel.com/changelog/cve-2025-57822">Vercel Changelog</a></p></blockquote> </details> <details> <summary>Release Notes</summary> <h4><a href="https://github.com/vercel/next.js/releases/tag/v15.4.7">15.4.7</a></h4> <blockquote><div class="markdown-alert markdown-alert-note" dir="auto"> <p class="markdown-alert-title" dir="auto"><svg class="octicon octicon-info mr-2" viewbox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path d="M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8Zm8-6.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13ZM6.5 7.75A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75ZM8 6a1 1 0 1 1 0-2 1 1 0 0 1 0 2Z"></path></svg>Note</p> <p dir="auto">This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </div> <h3 dir="auto">Core Changes</h3> <ul dir="auto"> <li>fix router handling when setting a location response header <a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82588">#82588</a> </li> </ul> <h3 dir="auto">Credits</h3> <p dir="auto">Huge thanks to <a href="https://bounce.depfu.com/github.com/ztanner">@ztanner</a> for helping!</p></blockquote> <h4><a href="https://github.com/vercel/next.js/releases/tag/v15.4.6">15.4.6</a></h4> <blockquote><div class="markdown-alert markdown-alert-note" dir="auto"> <p class="markdown-alert-title" dir="auto"><svg class="octicon octicon-info mr-2" viewbox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path d="M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8Zm8-6.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13ZM6.5 7.75A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75ZM8 6a1 1 0 1 1 0-2 1 1 0 0 1 0 2Z"></path></svg>Note</p> <p dir="auto">This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </div> <h3 dir="auto">Core Changes</h3> <ul dir="auto"> <li>fix: <code class="notranslate">_error</code> page's <code class="notranslate">req.url</code> can be overwritten to dynamic param on minimal mode (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82347">#82347</a>)</li> <li>fix: add <code class="notranslate">?dpl</code> to fonts in <code class="notranslate">/_next/static/media</code> (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82384">#82384</a>)</li> </ul> <h3 dir="auto">Credits</h3> <p dir="auto">Huge thanks to <a href="https://bounce.depfu.com/github.com/devjiwonchoi">@devjiwonchoi</a>, <a href="https://bounce.depfu.com/github.com/ijjk">@ijjk</a>, and <a href="https://bounce.depfu.com/github.com/styfle">@styfle</a> for helping!</p></blockquote> <h4><a href="https://github.com/vercel/next.js/releases/tag/v15.4.5">15.4.5</a></h4> <blockquote><div class="markdown-alert markdown-alert-note" dir="auto"> <p class="markdown-alert-title" dir="auto"><svg class="octicon octicon-info mr-2" viewbox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path d="M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8Zm8-6.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13ZM6.5 7.75A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75ZM8 6a1 1 0 1 1 0-2 1 1 0 0 1 0 2Z"></path></svg>Note</p> <p dir="auto">This release is backporting bug fixes. It does <strong>not</strong> include all pending features/changes on canary.</p> </div> <h3 dir="auto">Core Changes</h3> <ul dir="auto"> <li>Fix API stripping JSON incorrectly (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82062">#82062</a>)</li> <li>Fix i18n fallback: false collision (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82158">#82158</a>)</li> <li>Revert "Fix tracing of server actions imported by client components (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82167">#82167</a>)</li> <li>Ensure setAssetPrefix updates config instance (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82165">#82165</a>)</li> <li>Turbopack: update mimalloc (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82166">#82166</a>)</li> <li>fix(next/image): fix image-optimizer.ts headers (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82175">#82175</a>)</li> <li>fix(next/image): improve and simplify detect-content-type (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/82174">#82174</a>)</li> </ul> <h3 dir="auto">Credits</h3> <p dir="auto">Huge thanks to <a href="https://bounce.depfu.com/github.com/ijjk">@ijjk</a>, <a href="https://bounce.depfu.com/github.com/sokra">@sokra</a>, and <a href="https://bounce.depfu.com/github.com/styfle">@styfle</a> for helping!</p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/next/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href="https://github.com/vercel/next.js/compare/fe5db65859f0658d1c4701635ec4f4e5ec507e64...f30d815859e932e09222e93bb6e8a376b918d874">See the full diff on Github</a>. The new version differs by 14 commits:</p> <ul> <li><a href="https://github.com/vercel/next.js/commit/f30d815859e932e09222e93bb6e8a376b918d874"><code>v15.4.7</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/1a026e338d2b8c977c8949a134168952338d6d01"><code>fix router handling when setting a location response header (#82588)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/be4aafd4b744fbf6500b311b74c84243f70a3059"><code>v15.4.6</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/91e5b6b84f56c096dc2bb647eb384388e06489fd"><code>Backport &quot;fix: add `?dpl` to fonts in `/_next/static/media` (#82384)&quot; (#82421)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/f1629d939597cc46ccbe44fe66bda91eac31e219"><code>Backport &quot;[Pages] fix: `_error` page&#39;s `req.url` can be overwritten t… (#82377)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/b9aab5dbe926c256d439bfecb226693dcd1a1be4"><code>v15.4.5</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/a8c93c49dd2d42a2ced8a17bc53b3fea11d25c96"><code>Disable test new tests jobs</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/ed2a6c754831406f8cd724eb52a562bb124c1504"><code>[backport]: fix(next/image): improve and simplify detect-content-type (#82118) (#82174)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/f00fcc9011e7d0ef027021fc8424f51b8ac97880"><code>[backport]: fix(next/image): fix image-optimizer.ts headers (#82114) (#82175)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/55a7568e9d12459f8c5f5ae120fe2e228af284bb"><code>Backport: Turbopack: update mimalloc (#81993) (#82166)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/5bc4b368e5bc4d301f94955307e37a0328612408"><code>[backport] Ensure setAssetPrefix updates config instance (#82165)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/717dfb6ec985ba58b20ce6533ceecab213f72c22"><code>[Backport] Revert &quot;Fix tracing of server actions imported by client components (#78968) (#82167)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/6372ba03e85ca598b67fe21daa87dbad328f581b"><code>[backport] Fix i18n fallback: false collision (#82158)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/1e2c3792f88491ab8cfba580b8f17aad17015d17"><code>Fix API stripping JSON incorrectly (#82062)</code></a></li> </ul> </details> --- ![Depfu Status](https://depfu.com/badges/edd6acd35d74c8d41cbb540c30442adf/stats.svg) [Depfu](https://depfu.com) will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with `@depfu rebase`. <details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@​depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@​depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@​depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@​depfu cancel merge</dt><dd>Cancels automatic merging of this PR</dd> <dt>@​depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@​depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@​depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@​depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@​depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details> Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com>
2025-09-01 11:24:56 +02:00
"eslint-config-next": "^15.4.7",
Register `migrateImport` to ensure it actually runs (#14769) This PR makes sure the `migrateImport` codemod is properly registered so that it runs as part of the upgrade process. ## Test plan This PR adds a new `v3` playground with an `upgrade` script that you can use to run the upgrade from the local package. When you add a non-prefixed `@import` to the v3 example, the paths are now properly updated with no errors logged: https://github.com/user-attachments/assets/85949bbb-756b-4ee2-8ac0-234fe1b2ca39 --------- Co-authored-by: Adam Wathan <4323180+adamwathan@users.noreply.github.com> Co-authored-by: Philipp Spiess <hello@philippspiess.com>
2024-10-24 11:00:25 -04:00
"typescript": "^5.5.4"
}
}
Reference in a new issue Copy permalink