[Snyk] Fix for 1 vulnerabilities

[sestinj]

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

Snyk changed the following file(s):

• core/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Directory Traversal SNYK-JS-EXTRACTZIP-19653641	646

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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:

🦉 Directory Traversal

[sestinj]

This release includes major version upgrades for puppeteer and puppeteer-chromium-resolver, introducing significant breaking changes.

puppeteer 24.43.1 → 25.0.2 (High Risk)

This is a major update with several breaking changes that require developer action.

Key Breaking Changes:

• Node.js Version: Support for Node.js 18 is dropped. The minimum required version is now Node.js 20.19.
• ESM Only: The puppeteer packages are now ESM only. This may require changes to your import statements (e.g., from require() to import).
• API Removals & Changes:
  • Several deprecated methods and options have been removed, including MouseOptions.clickCount, Browser.isConnected(), and Puppeteer.product.
  • executablePath and defaultArgs now return a Promise.
  • Header handling has changed: newline-separated headers are normalized to a comma-separated format.

Recommendation:

• Ensure your environment uses Node.js v20.19 or newer.
• Update your project to handle ESM modules for puppeteer imports.
• Review your code for usage of the removed APIs and update accordingly.

puppeteer-chromium-resolver 23.0.0 → 25.0.0 (Medium Risk)

No explicit changelog was found for this package. However, given the major version jump and its close relationship with puppeteer, there is a moderate risk of breaking changes, likely to align with puppeteer v25.

Recommendation:

• Due to the lack of a detailed changelog, thorough testing is required to ensure compatibility with your existing implementation and the new puppeteer version.

Source: Puppeteer Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.