[Snyk] Upgrade @next/third-parties from 14.2.11 to 14.2.28

[sumansaurabh]

User description

Snyk has created this PR to upgrade @next/third-parties from 14.2.11 to 14.2.28.

ℹ️ 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 17 versions ahead of your current version.

• The recommended version was released 24 days ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BABELHELPERS-9397697	452	Proof of Concept
	Improper Input Validation SNYK-JS-NANOID-8492085	452	No Known Exploit
	Improper Authorization SNYK-JS-NEXT-9508709	452	Mature

Release notes

Package name: @next/third-parties

• 14.2.28 - 2025-04-08
  

  Note

  This release is backporting bug fixes. It does not include all pending features/changes on canary.

  Core Changes

  • fix: node.js module import error when using middleware (#77945)

  Credits

  Huge thanks to @ ztanner for helping!

• 14.2.27 - 2025-04-07
  

  Note

  This release is backporting bug fixes. It does not include all pending features/changes on canary.

  Core Changes

  • fix dynamic route interception not working when deployed with middleware (#64923)

  Credits

  Huge thanks to @ ztanner for helping!

• 14.2.26 - 2025-03-24
• 14.2.25 - 2025-03-17
• 14.2.24 - 2025-02-11
• 14.2.23 - 2025-01-07
• 14.2.22 - 2024-12-26
• 14.2.21 - 2024-12-19
• 14.2.20 - 2024-12-04
• 14.2.19 - 2024-12-03
• 14.2.18 - 2024-11-13
• 14.2.17 - 2024-11-05
• 14.2.16 - 2024-10-23
• 14.2.15 - 2024-10-08
• 14.2.14 - 2024-10-01
• 14.2.13 - 2024-09-20
• 14.2.12 - 2024-09-17
• 14.2.11 - 2024-09-12

from @next/third-parties GitHub release notes

---

Important

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

---

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
• 👩‍💻 Set who automatically gets assigned
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

---

Description

• Upgraded @next/third-parties to version 14.2.28 to address vulnerabilities.
• This upgrade enhances security by fixing known issues.

---

Changes walkthrough 📝

	Relevant files
Dependencies	package.json Upgrade @next/third-parties Dependency Version                      package.json Upgraded @next/third-parties dependency version from 14.2.5 to 14.2.28. +1/-1

---

💡 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]	1, because the change is a simple version upgrade in the dependencies with no complex logic involved.
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

[penify-dev]

PR Code Suggestions ✨

Category	Suggestion	Score
Maintainability	Use a specific version to prevent unexpected updates Consider using a specific version instead of a caret (^) to avoid unexpected updates in the future. package.json [15] -"@next/third-parties": "^14.2.28", +"@next/third-parties": "14.2.28", // Use specific version to prevent future issues Suggestion importance[1-10]: 7 Why: This suggestion provides a concrete code change that can improve maintainability by preventing unexpected updates, making it more actionable than the previous suggestions.	7
Compatibility	Verify compatibility of the upgraded dependency with existing packages Consider verifying the compatibility of the new version with your existing dependencies to avoid potential conflicts. package.json [15] -"@next/third-parties": "^14.2.28", +"@next/third-parties": "^14.2.28", // Ensure compatibility with other dependencies Suggestion importance[1-10]: 6 Why: While verifying compatibility is important, the suggestion does not provide a direct code change and is more of a general recommendation.	6
Best practice	Review the release notes for the new version to identify any breaking changes It may be beneficial to check the release notes for version 14.2.28 to understand any breaking changes or new features. package.json [15] -"@next/third-parties": "^14.2.28", +"@next/third-parties": "^14.2.28", // Review release notes for breaking changes Suggestion importance[1-10]: 6 Why: This suggestion emphasizes the importance of reviewing release notes, but it lacks a concrete code change and is more of a best practice guideline.	6
Testing	Update tests to ensure coverage of new features in the upgraded dependency Ensure that your testing suite is updated to cover any new features or changes introduced in the upgraded dependency. package.json [15] -"@next/third-parties": "^14.2.28", +"@next/third-parties": "^14.2.28", // Update tests for new features Suggestion importance[1-10]: 6 Why: Updating tests is crucial for maintaining code quality, but this suggestion does not directly modify the code and serves as a general reminder.	6