[Snyk] Upgrade puppeteer-cluster from 0.23.0 to 0.25.0

[rennokki]

Snyk has created this PR to upgrade puppeteer-cluster from 0.23.0 to 0.25.0.

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

• The recommended version was released 2 months ago.

Release notes

Package name: puppeteer-cluster

• 0.25.0 - 2025-11-13
  

  Note: Use a version older than 0.25.0 if you want to use a puppeteer version older than 24.0.0.

  Changed

  • Updated puppeteer types to version 24
  • Updated dependencies to their latest versions
  • Exported more types for improved TypeScript use

  Fixed

  • Cluster retrying in error cases when it was already closed
• 0.24.0 - 2024-03-17
  

  Note: Use a version older than 0.24.0 if you want to use a puppeteer version older than 22.0.0.

  Changed

  • Updated all dependencies to their latest versions
  • Added a missing timeout case when closing the browser
  • Removed package-lock.json as otherwise yarn complains (warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.).
  • Dropped support (in tests) for Node.js <=16 as puppeteer also support for these versions

  Fixed

  • Fixed breaking puppeteer changes introduced in version 22 (renamed createIncognitoBrowserContext to createBrowserContext)
• 0.23.0 - 2022-01-23
  

  Changed

  • Updated dependencies which haven't been updated for more than one year
  • Moved from Travis to Github Actions
  • Remove the linter for now, but will probably add it back later after having a look at the pull requests.

  Fixed

  • Fixed bug #395 not using perBrowserOptions

from puppeteer-cluster 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.

---

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
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[gemini-code-assist]

Summary of Changes

Hello @rennokki, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates the upgrade of the puppeteer-cluster dependency to its latest stable version, 0.25.0. The primary goal is to enhance the project's security posture and maintainability by incorporating the most recent bug fixes, dependency updates, and compatibility improvements, particularly with newer versions of Puppeteer. This ensures the application leverages the latest features and stability enhancements from the puppeteer-cluster library.

Highlights

• Dependency Upgrade: The puppeteer-cluster package has been upgraded from version 0.23.0 to 0.25.0 to ensure dependencies are kept up-to-date and secure.
• Puppeteer Compatibility: This upgrade includes updates to puppeteer types to version 24 and fixes for breaking changes introduced in Puppeteer version 22, such as the renaming of createIncognitoBrowserContext to createBrowserContext.
• Dependency Updates & Bug Fixes: All underlying dependencies of puppeteer-cluster have been updated to their latest versions, and a fix for the cluster retrying in error cases when it was already closed has been included.
• Node.js Support Alignment: Support for Node.js versions less than or equal to 16 has been dropped in puppeteer-cluster's tests, aligning with Puppeteer's own support.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades puppeteer-cluster to version 0.25.0. However, this upgrade introduces a critical compatibility issue. The new version of puppeteer-cluster requires puppeteer version 22.0.0 or higher, while the project currently uses ^5.5.0. This version mismatch will cause the application to fail. I've added a critical comment on package.json suggesting to upgrade puppeteer as well, and warning about potential breaking changes in the puppeteer API that will need to be addressed in server.js.

[gemini-code-assist]

This upgrade to [email protected] is incompatible with the puppeteer version (^5.5.0) currently in use. As stated in the release notes and its peerDependencies, [email protected] requires puppeteer@>=22.0.0.

To resolve this incompatibility, the puppeteer dependency must also be upgraded.

Important Note: Upgrading puppeteer from version 5 to a much later version will require code changes due to breaking API changes. For example, the private API page._client used in server.js:217 is no longer available in recent puppeteer versions and should be replaced with the public page.cookies() method. Please carefully review the puppeteer changelogs for other breaking changes and update your code accordingly.

Suggested change

	"puppeteer": "^5.5.0",
	"puppeteer-cluster": "^0.23.0",
	"puppeteer-cluster": "^0.25.0",
	"puppeteer": "^24.0.0",
	"puppeteer-cluster": "^0.25.0",

[Copilot]

Pull request overview

This PR upgrades puppeteer-cluster from version 0.23.0 to 0.25.0 as an automated Snyk dependency update. However, this upgrade introduces a critical compatibility issue that will prevent the application from working correctly.

Key Changes:

• Upgrade puppeteer-cluster dependency from ^0.23.0 to ^0.25.0
• Introduces incompatibility with the current puppeteer version (5.5.0 vs required 24.0.0+)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The upgrade to puppeteer-cluster 0.25.0 is incompatible with the current puppeteer version. According to the release notes, puppeteer-cluster 0.25.0 requires puppeteer version 24.0.0 or higher, but this project is using puppeteer version 5.5.0. This version mismatch will likely cause runtime errors and API incompatibilities. You need to either upgrade puppeteer to version 24.0.0 or higher, or use puppeteer-cluster version 0.23.0.

Suggested change

	"puppeteer-cluster": "^0.25.0",
	"puppeteer-cluster": "^0.23.0",