-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Comparing changes
Open a pull request
base repository: tailwindlabs/tailwindcss
base: v4.1.16
head repository: tailwindlabs/tailwindcss
compare: v4.1.17
- 13 commits
- 32 files changed
- 4 contributors
Commits on Oct 23, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 2530934 - Browse repository at this point
Copy the full SHA 2530934View commit details
Commits on Oct 24, 2025
-
Update all of nextjs 15.5.4 → 15.5.6 (patch) (#19194)
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.5.4 → 15.5.6) Sorry, we couldn't find anything useful about this release. #### ✳️ next (15.5.4 → 15.5.6) · [Repo](https://github.com/vercel/next.js) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/vercel/next.js/releases/tag/v15.5.6">15.5.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>Turbopack: don't define process.cwd() in node_modules <a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/83452">#83452</a> </li> </ul> <h3 dir="auto">Credits</h3> <p dir="auto">Huge thanks to <a href="https://bounce.depfu.com/github.com/mischnic">@mischnic</a> for helping!</p></blockquote> <h4><a href="https://github.com/vercel/next.js/releases/tag/v15.5.5">15.5.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>Split code-frame into separate compiled package (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/84238">#84238</a>)</li> <li>Add deprecation warning to Runtime config (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/84650">#84650</a>)</li> <li>fix: unstable_cache should perform blocking revalidation during ISR revalidation (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/84716">#84716</a>)</li> <li>feat: <code class="notranslate">experimental.middlewareClientMaxBodySize</code> body cloning limit (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/84722">#84722</a>)</li> <li>fix: missing next/link types with typedRoutes (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/84779">#84779</a>)</li> </ul> <h3 dir="auto">Misc Changes</h3> <ul dir="auto"> <li>docs: early October improvements and fixes (<a href="https://bounce.depfu.com/github.com/vercel/next.js/pull/84334">#84334</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/ztanner">@ztanner</a>, and <a href="https://bounce.depfu.com/github.com/icyJoseph">@icyJoseph</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/40f1d7814d8f1ab3d9e169b389015b8d6f258fb3...55ef0e3ebc1d43e1a4a191341dc2a415e12124d4">See the full diff on Github</a>. The new version differs by 10 commits:</p> <ul> <li><a href="https://github.com/vercel/next.js/commit/55ef0e3ebc1d43e1a4a191341dc2a415e12124d4"><code>v15.5.6</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/92bbbb1beca8738c783ea36ee5dd84d89cd638be"><code>Backport: don't define `process.cwd()` in node_modules (#84957)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/f895b727626ad921d5068bcfada284f68c998bfa"><code>Fix url-imports test on 15-5 (#84966)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/81f530db2652a96d4b88fabaf4dfaf30c2269695"><code>v15.5.5</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/9abbc0e9eba67d635d4da5293273de123263101d"><code>[backport] fix: missing `next/link` types with `typedRoutes` (#82814) (#84779)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/121e1b566f8bf632dd09bf06fbbdb5ff5a21a51c"><code>[backport] docs: early October improvements and fixes (#84334)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/1b276c98f98f2d06bb9be36634410851867b013f"><code>[backport]: `experimental.middlewareClientMaxBodySize` (#84722)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/2061f04132690956ac0722eeacdff8747d7c1c49"><code>[backport] fix: unstable_cache should perform blocking revalidation during ISR revalidation (#84716)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/ce3d9639d12eaa0fe05ba5cbc7a5d86daf3b3341"><code>[backport] Add deprecation warning to Runtime config (#84168) (#84650)</code></a></li> <li><a href="https://github.com/vercel/next.js/commit/ec69752d9e5b4174491cdded7b419ba7657db481"><code>[backport] Split code-frame into separate compiled package (#84174) (#84238)</code></a></li> </ul> </details> ---  [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>
Configuration menu - View commit details
-
Copy full SHA for effcd27 - Browse repository at this point
Copy the full SHA effcd27View commit details -
Configuration menu - View commit details
-
Copy full SHA for 91694fb - Browse repository at this point
Copy the full SHA 91694fbView commit details
Commits on Oct 28, 2025
-
Update @emnapi/runtime 1.5.0 → 1.6.0 (minor) (#19219)
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? #### ✳️ @emnapi/runtime (1.5.0 → 1.6.0) · [Repo](https://github.com/toyobayashi/emnapi) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/toyobayashi/emnapi/releases/tag/v1.6.0">1.6.0</a></h4> <blockquote><h2 dir="auto">What's Changed</h2> <ul dir="auto"> <li>feat: added SharedArrayBuffer api by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/171">#171</a> </li> <li>feat: make napi_delete_reference use node_api_basic_env by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/170">#170</a> </li> <li>ci: migrate to npm trusted publishing by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/168">#168</a> </li> </ul> <p dir="auto"><strong>Full Changelog</strong>: <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/compare/v1.5.0...v1.6.0"><tt>v1.5.0...v1.6.0</tt></a></p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/@emnapi%2Fruntime/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href="https://github.com/toyobayashi/emnapi/compare/61628bd5e27679955f13cbff8f6573d66a5fc00c...86d68f88ec3cc3949a555c93a633fa8997534413">See the full diff on Github</a>. The new version differs by 4 commits:</p> <ul> <li><a href="https://github.com/toyobayashi/emnapi/commit/86d68f88ec3cc3949a555c93a633fa8997534413"><code>1.6.0</code></a></li> <li><a href="https://github.com/toyobayashi/emnapi/commit/100b8a358091a930cb189081f4dd900dc6bf2998"><code>feat: make napi_delete_reference use node_api_basic_env (#170)</code></a></li> <li><a href="https://github.com/toyobayashi/emnapi/commit/bf622fc37b250c05e31629bc7591aeb4cdb48415"><code>[Backport] feat: added SharedArrayBuffer api (#171)</code></a></li> <li><a href="https://github.com/toyobayashi/emnapi/commit/971e3d9e37e0157e26cf4906c230cd3dd2072393"><code>ci: migrate to npm trusted publishing (#168)</code></a></li> </ul> </details> ---  [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>
Configuration menu - View commit details
-
Copy full SHA for 7bab613 - Browse repository at this point
Copy the full SHA 7bab613View commit details -
Update emnapi 1.5.0 → 1.6.0 (minor) (#19221)
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request. ### What changed? #### ✳️ emnapi (1.5.0 → 1.6.0) · [Repo](https://github.com/toyobayashi/emnapi) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/toyobayashi/emnapi/releases/tag/v1.6.0">1.6.0</a></h4> <blockquote><h2 dir="auto">What's Changed</h2> <ul dir="auto"> <li>feat: added SharedArrayBuffer api by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/171">#171</a> </li> <li>feat: make napi_delete_reference use node_api_basic_env by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/170">#170</a> </li> <li>ci: migrate to npm trusted publishing by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/168">#168</a> </li> </ul> <p dir="auto"><strong>Full Changelog</strong>: <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/compare/v1.5.0...v1.6.0"><tt>v1.5.0...v1.6.0</tt></a></p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/emnapi/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href="https://github.com/toyobayashi/emnapi/compare/61628bd5e27679955f13cbff8f6573d66a5fc00c...86d68f88ec3cc3949a555c93a633fa8997534413">See the full diff on Github</a>. The new version differs by 4 commits:</p> <ul> <li><a href="https://github.com/toyobayashi/emnapi/commit/86d68f88ec3cc3949a555c93a633fa8997534413"><code>1.6.0</code></a></li> <li><a href="https://github.com/toyobayashi/emnapi/commit/100b8a358091a930cb189081f4dd900dc6bf2998"><code>feat: make napi_delete_reference use node_api_basic_env (#170)</code></a></li> <li><a href="https://github.com/toyobayashi/emnapi/commit/bf622fc37b250c05e31629bc7591aeb4cdb48415"><code>[Backport] feat: added SharedArrayBuffer api (#171)</code></a></li> <li><a href="https://github.com/toyobayashi/emnapi/commit/971e3d9e37e0157e26cf4906c230cd3dd2072393"><code>ci: migrate to npm trusted publishing (#168)</code></a></li> </ul> </details> ---  [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>
Configuration menu - View commit details
-
Copy full SHA for 4aa763b - Browse repository at this point
Copy the full SHA 4aa763bView commit details -
Update @emnapi/core 1.5.0 → 1.6.0 (minor) (#19220)
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? #### ✳️ @emnapi/core (1.5.0 → 1.6.0) · [Repo](https://github.com/toyobayashi/emnapi) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/toyobayashi/emnapi/releases/tag/v1.6.0">1.6.0</a></h4> <blockquote><h2 dir="auto">What's Changed</h2> <ul dir="auto"> <li>feat: added SharedArrayBuffer api by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/171">#171</a> </li> <li>feat: make napi_delete_reference use node_api_basic_env by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/170">#170</a> </li> <li>ci: migrate to npm trusted publishing by <a href="https://bounce.depfu.com/github.com/toyobayashi">@toyobayashi</a> in <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/pull/168">#168</a> </li> </ul> <p dir="auto"><strong>Full Changelog</strong>: <a href="https://bounce.depfu.com/github.com/toyobayashi/emnapi/compare/v1.5.0...v1.6.0"><tt>v1.5.0...v1.6.0</tt></a></p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/@emnapi%2Fcore/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href="https://github.com/toyobayashi/emnapi/compare/61628bd5e27679955f13cbff8f6573d66a5fc00c...86d68f88ec3cc3949a555c93a633fa8997534413">See the full diff on Github</a>. The new version differs by 4 commits:</p> <ul> <li><a href="https://github.com/toyobayashi/emnapi/commit/86d68f88ec3cc3949a555c93a633fa8997534413"><code>1.6.0</code></a></li> <li><a href="https://github.com/toyobayashi/emnapi/commit/100b8a358091a930cb189081f4dd900dc6bf2998"><code>feat: make napi_delete_reference use node_api_basic_env (#170)</code></a></li> <li><a href="https://github.com/toyobayashi/emnapi/commit/bf622fc37b250c05e31629bc7591aeb4cdb48415"><code>[Backport] feat: added SharedArrayBuffer api (#171)</code></a></li> <li><a href="https://github.com/toyobayashi/emnapi/commit/971e3d9e37e0157e26cf4906c230cd3dd2072393"><code>ci: migrate to npm trusted publishing (#168)</code></a></li> </ul> </details> ---  [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>
Configuration menu - View commit details
-
Copy full SHA for 4827c46 - Browse repository at this point
Copy the full SHA 4827c46View commit details
Commits on Oct 31, 2025
-
Update magic-string 0.30.19 → 0.30.21 (minor) (#19238)
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? #### ✳️ magic-string (0.30.19 → 0.30.21) · [Repo](https://github.com/rich-harris/magic-string) · [Changelog](https://github.com/Rich-Harris/magic-string/blob/master/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4><a href="https://github.com/Rich-Harris/magic-string/releases/tag/v0.30.21">0.30.21</a></h4> <blockquote><p dir="auto"><em>No significant changes</em></p> <h5 dir="auto"> <a href="https://bounce.depfu.com/github.com/Rich-Harris/magic-string/compare/v0.30.20...v0.30.21">View changes on GitHub</a> </h5></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/magic-string/feedback">Please let us know.</a></em></p> </details> <details> <summary>Commits</summary> <p><a href="https://github.com/rich-harris/magic-string/compare/bdef7d5ab5087f279d999a9c148f0c5c3a64259e...410fd4d080d8bf0b5be900c16c8ba11276fd8749">See the full diff on Github</a>. The new version differs by 7 commits:</p> <ul> <li><a href="https://github.com/Rich-Harris/magic-string/commit/410fd4d080d8bf0b5be900c16c8ba11276fd8749"><code>chore: release v0.30.21</code></a></li> <li><a href="https://github.com/Rich-Harris/magic-string/commit/5c1800935d7d572d57bf5ae70f0d452661fa6ee9"><code>chore: update repository url</code></a></li> <li><a href="https://github.com/Rich-Harris/magic-string/commit/97ea74d842ae8b942289c672150b0609ee99f762"><code>chore: release v0.30.20</code></a></li> <li><a href="https://github.com/Rich-Harris/magic-string/commit/3f6b5eb3fbefbcbeb1298c068f50c7445becbe7d"><code>chore: update deps</code></a></li> <li><a href="https://github.com/Rich-Harris/magic-string/commit/60177d51ed3bb11dc5ab2019b176e35c5b490cd2"><code>ci: setup OIDC</code></a></li> <li><a href="https://github.com/Rich-Harris/magic-string/commit/fbcf5d7e59c232016ac98025b044e2772fcfeeb2"><code>chore: create release.yml</code></a></li> <li><a href="https://github.com/Rich-Harris/magic-string/commit/cde8c33ef5ef05dec95dadd817609e5de95d159b"><code>chore: update readme (#305)</code></a></li> </ul> </details> ---  [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>
Configuration menu - View commit details
-
Copy full SHA for e71e70e - Browse repository at this point
Copy the full SHA e71e70eView commit details -
Update @vitejs/plugin-react 5.0.4 → 5.1.0 (minor) (#19241)
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? #### ✳️ @vitejs/plugin-react (5.0.4 → 5.1.0) · [Repo](https://github.com/vitejs/vite-plugin-react) · [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md) <details> <summary>Release Notes</summary> <h4>5.1.0 (from changelog)</h4> <blockquote><h3 dir="auto">Add <code class="notranslate">@vitejs/plugin-react/preamble</code> virtual module for SSR HMR (<a href="https://bounce.depfu.com/github.com/vitejs/vite-plugin-react/pull/890">#890</a>)</h3> <p dir="auto">SSR applications can now initialize HMR runtime by importing <code class="notranslate">@vitejs/plugin-react/preamble</code> at the top of their client entry instead of manually calling <code class="notranslate">transformIndexHtml</code>. This simplifies SSR setup for applications that don't use the <code class="notranslate">transformIndexHtml</code> API.</p></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/@vitejs%2Fplugin-react/feedback">Please let us know.</a></em></p> </details> ---  [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>
Configuration menu - View commit details
-
Copy full SHA for 604c22f - Browse repository at this point
Copy the full SHA 604c22fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 3cece1d - Browse repository at this point
Copy the full SHA 3cece1dView commit details
Commits on Nov 4, 2025
-
Update @types/react-dom 19.2.1 → 19.2.2 (patch) (#19259)
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.2.1 → 19.2.2) · [Repo](https://github.com/DefinitelyTyped/DefinitelyTyped) Sorry, we couldn't find anything useful about this release. ---  [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>
Configuration menu - View commit details
-
Copy full SHA for 3e4654d - Browse repository at this point
Copy the full SHA 3e4654dView commit details -
Configuration menu - View commit details
-
Copy full SHA for babe825 - Browse repository at this point
Copy the full SHA babe825View commit details -
Configuration menu - View commit details
-
Copy full SHA for dc6a3ce - Browse repository at this point
Copy the full SHA dc6a3ceView commit details
Commits on Nov 6, 2025
-
Configuration menu - View commit details
-
Copy full SHA for e9c9c4f - Browse repository at this point
Copy the full SHA e9c9c4fView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v4.1.16...v4.1.17