[Snyk] Upgrade next from 12.3.1 to 12.3.4

[maidul98]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade next from 12.3.1 to 12.3.4.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 40 versions ahead of your current version.
• The recommended version was released a month ago, on 2022-11-21.

Release notes

Package name: next

• 12.3.4 - 2022-11-21
  

  v12.3.4

• 12.3.3 - 2022-11-09
• 12.3.2 - 2022-10-30
• 12.3.2-canary.43 - 2022-10-25
• 12.3.2-canary.42 - 2022-10-25
• 12.3.2-canary.41 - 2022-10-25
• 12.3.2-canary.40 - 2022-10-25
• 12.3.2-canary.39 - 2022-10-24
• 12.3.2-canary.38 - 2022-10-24
• 12.3.2-canary.35 - 2022-10-23
• 12.3.2-canary.34 - 2022-10-23
• 12.3.2-canary.33 - 2022-10-22
• 12.3.2-canary.32 - 2022-10-19
• 12.3.2-canary.31 - 2022-10-19
• 12.3.2-canary.30 - 2022-10-18
• 12.3.2-canary.29 - 2022-10-16
• 12.3.2-canary.28 - 2022-10-13
• 12.3.2-canary.27 - 2022-10-13
• 12.3.2-canary.26 - 2022-10-12
• 12.3.2-canary.25 - 2022-10-11
• 12.3.2-canary.24 - 2022-10-11
• 12.3.2-canary.23 - 2022-10-08
• 12.3.2-canary.22 - 2022-10-07
• 12.3.2-canary.21 - 2022-10-06
• 12.3.2-canary.20 - 2022-10-05
• 12.3.2-canary.19 - 2022-10-04
• 12.3.2-canary.18 - 2022-10-04
• 12.3.2-canary.17 - 2022-10-02
• 12.3.2-canary.16 - 2022-09-30
• 12.3.2-canary.15 - 2022-09-29
• 12.3.2-canary.13 - 2022-09-29
• 12.3.2-canary.12 - 2022-09-28
• 12.3.2-canary.11 - 2022-09-27
• 12.3.2-canary.10 - 2022-09-27
• 12.3.2-canary.9 - 2022-09-26
• 12.3.2-canary.7 - 2022-09-23
• 12.3.2-canary.6 - 2022-09-23
• 12.3.2-canary.3 - 2022-09-22
• 12.3.2-canary.2 - 2022-09-22
• 12.3.2-canary.0 - 2022-09-21
• 12.3.1 - 2022-09-19

from next GitHub release notes

Commit messages

Package name: next

• e2c5952 v12.3.4
• 4006812 Update experimental skipTrailingSlashRedirect handling
• be75d09 v12.3.3
• 623622f Update swc builds
• 0381cf0 Add missing matcher support
• b9c7408 Apply normalize patch
• 1b8ab4e Apply middleware patches
• 58dcf30 Apply fix(stream): Allows body larger than 16 KiB with middleware
• f3fc912 v12.3.2
• 3e0f0d6 lock docker image
• 9ab1166 apply changes for publish
• e7208a1 [edge] serialize custom config to middleware-manifest

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
5324534	Generic High Entropy Secret	b8e5a2c	.env.example	View secret
5324535	Generic High Entropy Secret	b8e5a2c	.env.example	View secret
5324536	Generic High Entropy Secret	b8e5a2c	.env.example	View secret
5324537	Generic High Entropy Secret	b8e5a2c	.env.example	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>