Bump next from 9.4.4 to 12.0.7 in /client #31

Open

dependabot[bot] wants to merge 1 commit from dependabot/npm_and_yarn/client/next-12.0.7 into master

dependabot[bot] commented

2021-12-09 01:44:54 +00:00

(Migrated from github.com)

Bumps next from 9.4.4 to 12.0.7.

Release notes

Sourced from next's releases.

v12.0.7

Core Changes

Add test for TailwindCSS JIT mode reloading: #32130

Ensure conf type for createServer is not changed: #32134

Credits

Huge thanks to @timneutkens for helping!

v12.0.7-canary.0

Core Changes

Add test for TailwindCSS JIT mode reloading: #32130

Ensure conf type for createServer is not changed: #32134

Credits

Huge thanks to @timneutkens for helping!

v12.0.6

Core Changes

Fix document type import path: #32117

v12.0.6-canary.0

Core Changes

Fix document type import path: #32117

v12.0.5

This upgrade is completely backward-compatible and recommended for all users on versions below 12.0.5. A backport of the patch to Next.js 11 is available as 11.1.3.

When a URL is provided to next-server that cannot be parsed, an unhandledPromiseRejection could occur. On Node.js versions v15.0.0, this causes the server process to exit, which can result in unexpected server crashes.

How to Upgrade

We have released patch versions for both the stable and canary channels of Next.js.

To upgrade run npm install next@latest --save

Impact

Affected: All of the following must be true to be affected

Next.js versions above v11.1.0 and below v12.0.5

Node.js above v15.0.0 being used

Using next start or a custom server

Not affected: Deployments on Vercel (vercel.com) are not affected along with similar environments where invalid requests are filtered before reaching Next.js.

We recommend everyone to upgrade regardless of whether you can reproduce the issue or not.

... (truncated)

Commits

ebf5095 v12.0.7
1e21c7d v12.0.7-canary.0
769d680 Ensure conf type for createServer is not changed (#32134)
c1a1aa4 Add test for TailwindCSS JIT mode reloading (#32130)
56c68db v12.0.6
e257dbf v12.0.6-canary.0
980e169 Fix document type import path (#32117)
b6162bb v12.0.5
1705020 v12.0.5-canary.19
f0fd496 Revert "Fix running server with Polyfilled fetch (#31935)" (#32100)
Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by vercel-release-bot, a new releaser for next since your current version.

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 commands and options

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 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)
@dependabot use these labels will set the current labels as the default for future PRs for this repo and language
@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [next](https://github.com/vercel/next.js) from 9.4.4 to 12.0.7. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vercel/next.js/releases">next's releases</a>.</em></p> <blockquote> <h2>v12.0.7</h2> <h3>Core Changes</h3> <ul> <li>Add test for TailwindCSS JIT mode reloading: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/32130">#32130</a></li> <li>Ensure conf type for createServer is not changed: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/32134">#32134</a></li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/timneutkens"><code>@timneutkens</code></a> for helping!</p> <h2>v12.0.7-canary.0</h2> <h3>Core Changes</h3> <ul> <li>Add test for TailwindCSS JIT mode reloading: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/32130">#32130</a></li> <li>Ensure conf type for createServer is not changed: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/32134">#32134</a></li> </ul> <h3>Credits</h3> <p>Huge thanks to <a href="https://github.com/timneutkens"><code>@timneutkens</code></a> for helping!</p> <h2>v12.0.6</h2> <h3>Core Changes</h3> <ul> <li>Fix document type import path: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/32117">#32117</a></li> </ul> <h2>v12.0.6-canary.0</h2> <h3>Core Changes</h3> <ul> <li>Fix document type import path: <a href="https://github-redirect.dependabot.com/vercel/next.js/issues/32117">#32117</a></li> </ul> <h2>v12.0.5</h2> <p><strong>This upgrade is completely backward-compatible and recommended for all users on versions below 12.0.5. A backport of the patch to Next.js 11 is available as 11.1.3.</strong></p> <p>When a URL is provided to <code>next-server</code> that cannot be parsed, an <code>unhandledPromiseRejection</code> could occur. On Node.js versions  <code>v15.0.0</code>, this causes the server process to exit, which can result in unexpected server crashes.</p> <h2>How to Upgrade</h2> <ul> <li>We have released patch versions for both the stable and canary channels of Next.js.</li> <li>To upgrade run <code>npm install next@latest --save</code></li> </ul> <h2>Impact</h2> <ul> <li><strong>Affected:</strong> All of the following must be true to be affected <ul> <li>Next.js versions above <code>v11.1.0</code> and below <code>v12.0.5</code></li> <li>Node.js above <code>v15.0.0</code> being used</li> <li>Using <code>next start</code> or a <a href="https://nextjs.org/docs/advanced-features/custom-server">custom server</a></li> </ul> </li> <li><strong>Not affected</strong>: Deployments on Vercel (<a href="https://vercel.com">vercel.com</a>) are not affected along with similar environments where invalid requests are filtered before reaching Next.js.</li> </ul> <p>We recommend everyone to upgrade regardless of whether you can reproduce the issue or not.</p>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vercel/next.js/commit/ebf509539c0f4f519923c7780e269872059c384e"><code>ebf5095</code></a> v12.0.7</li> <li><a href="https://github.com/vercel/next.js/commit/1e21c7df13e720fdc34dd122de370e8a50591379"><code>1e21c7d</code></a> v12.0.7-canary.0</li> <li><a href="https://github.com/vercel/next.js/commit/769d68047bf61cf40f178da08da3c2a98732df7b"><code>769d680</code></a> Ensure conf type for createServer is not changed (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/32134">#32134</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/c1a1aa4ae2e0ba5d7c4ba023686c29d592c60c87"><code>c1a1aa4</code></a> Add test for TailwindCSS JIT mode reloading (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/32130">#32130</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/56c68dba518843576330e1d9461ceeb38371aadd"><code>56c68db</code></a> v12.0.6</li> <li><a href="https://github.com/vercel/next.js/commit/e257dbfad5d3b50ed47cdb6b240acfe7fde0ee64"><code>e257dbf</code></a> v12.0.6-canary.0</li> <li><a href="https://github.com/vercel/next.js/commit/980e16998cab8f81ae3150bf47de5c4d912105ba"><code>980e169</code></a> Fix document type import path (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/32117">#32117</a>)</li> <li><a href="https://github.com/vercel/next.js/commit/b6162bb6b6b46788ef2ae700d81c99e94d903900"><code>b6162bb</code></a> v12.0.5</li> <li><a href="https://github.com/vercel/next.js/commit/170502080856993e23fee0e9a418ae11a1f21e77"><code>1705020</code></a> v12.0.5-canary.19</li> <li><a href="https://github.com/vercel/next.js/commit/f0fd4962e9ec1e60274501ef511a4b5468a374f6"><code>f0fd496</code></a> Revert "Fix running server with Polyfilled fetch (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/31935">#31935</a>)" (<a href="https://github-redirect.dependabot.com/vercel/next.js/issues/32100">#32100</a>)</li> <li>Additional commits viewable in <a href="https://github.com/vercel/next.js/compare/v9.4.4...v12.0.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/~vercel-release-bot">vercel-release-bot</a>, a new releaser for next since your current version.</p> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=next&package-manager=npm_and_yarn&previous-version=9.4.4&new-version=12.0.7)](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 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/RileySeaburg/nextjs-strapi-blog-starter/network/alerts). </details>

codetether[bot] commented

2026-06-04 16:19:50 +00:00

(Migrated from github.com)

🛠️ CodeTether Fix

Picked up this request for PR #31 on branch dependabot/npm_and_yarn/client/next-12.0.7. I’m preparing the workspace and will push changes directly to the existing PR branch if the task succeeds. I will also make sure the branch is mergeable with master.

## 🛠️ CodeTether Fix Picked up this request for PR #31 on branch `dependabot/npm_and_yarn/client/next-12.0.7`. I’m preparing the workspace and will push changes directly to the existing PR branch if the task succeeds. I will also make sure the branch is mergeable with `master`.

This pull request can be merged automatically.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin dependabot/npm_and_yarn/client/next-12.0.7:dependabot/npm_and_yarn/client/next-12.0.7

git switch dependabot/npm_and_yarn/client/next-12.0.7

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master

git merge --no-ff dependabot/npm_and_yarn/client/next-12.0.7

git switch dependabot/npm_and_yarn/client/next-12.0.7

git rebase master

git switch master

git merge --ff-only dependabot/npm_and_yarn/client/next-12.0.7

git switch dependabot/npm_and_yarn/client/next-12.0.7

git rebase master

git switch master

git merge --no-ff dependabot/npm_and_yarn/client/next-12.0.7

git switch master

git merge --squash dependabot/npm_and_yarn/client/next-12.0.7