[Snyk] Security upgrade eslint-config-next from 13.1.2 to 15.0.0

[sumansaurabh]

User description

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• apps/file-q-and-a/nextjs-with-flask-server/client/package.json
• apps/file-q-and-a/nextjs-with-flask-server/client/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-SEMVER-3247795	696

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)

---

Description

• Upgraded eslint-config-next to address security vulnerabilities.
• This change fixes a Regular Expression Denial of Service (ReDoS) vulnerability.
• Updated package-lock.json to ensure consistency with the new package version.

---

Changes walkthrough 📝

Relevant files

Enhancement

package.json Upgrade eslint-config-next for improved security                  apps/file-q-and-a/nextjs-with-flask-server/client/package.json Upgraded eslint-config-next from version 13.1.2 to 15.0.0. +1/-1      package-lock.json Update package-lock.json for dependency changes                    apps/file-q-and-a/nextjs-with-flask-server/client/package-lock.json Updated lockfile to reflect changes in package.json. +3081/-1296

---

💡 Penify usage:
Comment /help on the PR to get a list of all available Penify tools and their descriptions

[penify-dev]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	2, because the changes are straightforward, involving a version upgrade of a dependency with no significant code alterations.
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

[penify-dev]

Failed to generate code suggestions for PR