npm: bump puppeteer from 13.7.0 to 24.25.0

[dependabot]

Bumps puppeteer from 13.7.0 to 24.25.0.

Release notes

Sourced from puppeteer's releases.

puppeteer-core: v24.25.0

24.25.0 (2025-10-15)

Features

• roll to Firefox 144.0 (#14322) (9d1ad07)

Bug Fixes

• roll to Chrome 141.0.7390.78 (#14321) (064145c)

puppeteer: v24.25.0

24.25.0 (2025-10-15)

Miscellaneous Chores

• puppeteer: Synchronize puppeteer versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • puppeteer-core bumped from 24.24.1 to 24.25.0

puppeteer-core: v24.24.1

24.24.1 (2025-10-13)

Bug Fixes

• detect missing X11 server and report errors (#14306) (74c551b)
• Revert "fix(webdriver): response should be created on responseStarted" (#14312) (abb8ee0)
• revert Accessibility heuristic focus changes (#14313) (8b1706a)
• webdriver: response should be created on responseStarted (#14302) (c86e367)
• windows: use lockfile to detect concurrent chrome instances (#14307) (8d3a60b)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​puppeteer/browsers bumped from 2.10.11 to 2.10.12

puppeteer: v24.24.1

24.24.1 (2025-10-13)

... (truncated)

Changelog

Sourced from puppeteer's changelog.

24.25.0 (2025-10-15)

Miscellaneous Chores

• puppeteer: Synchronize puppeteer versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • puppeteer-core bumped from 24.24.1 to 24.25.0

Features

• roll to Firefox 144.0 (#14322) (9d1ad07)

Bug Fixes

• roll to Chrome 141.0.7390.78 (#14321) (064145c)

24.24.1 (2025-10-13)

Miscellaneous Chores

• puppeteer: Synchronize puppeteer versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​puppeteer/browsers bumped from 2.10.11 to 2.10.12

Bug Fixes

• detect missing X11 server and report errors (#14306) (74c551b)
• Revert "fix(webdriver): response should be created on responseStarted" (#14312) (abb8ee0)
• revert Accessibility heuristic focus changes (#14313) (8b1706a)
• webdriver: response should be created on responseStarted (#14302) (c86e367)
• windows: use lockfile to detect concurrent chrome instances (#14307) (8d3a60b)

24.24.0 (2025-10-10)

... (truncated)

Commits

• 7d3f881 chore: fix typo (#14326)
• d16ded2 chore: release main (#14323)
• 9d1ad07 feat: roll to Firefox 144.0 (#14322)
• a6f7839 chore: migrate to Trusted Publishing with provenance attestation (#14324)
• 064145c fix: roll to Chrome 141.0.7390.78 (#14321)
• 67b1764 chore: release main (#14311)
• 8b1706a fix: revert Accessibility heuristic focus changes (#14313)
• abb8ee0 fix: Revert "fix(webdriver): response should be created on responseStarted" (...
• 5d27978 refactor: use release-please to manage version (#14310)
• c86e367 fix(webdriver): response should be created on responseStarted (#14302)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for puppeteer since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: npm. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		ejs@2.7.4 has a Critical CVE. CVE: GHSA-phwq-j96m-2c2q ejs template injection vulnerability (CRITICAL) Affected versions: < 3.1.7 Patched version: 3.1.7 From: ? → npm/ejs@2.7.4 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/ejs@2.7.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[dependabot]

Superseded by #3507.