Bump puppeteer from 24.43.1 to 25.0.3 in the puppeteer group#218
Conversation
Bumps the puppeteer group with 1 update: [puppeteer](https://github.com/puppeteer/puppeteer). Updates `puppeteer` from 24.43.1 to 25.0.3 - [Release notes](https://github.com/puppeteer/puppeteer/releases) - [Changelog](https://github.com/puppeteer/puppeteer/blob/main/CHANGELOG.md) - [Commits](puppeteer/puppeteer@puppeteer-v24.43.1...puppeteer-v25.0.3) --- updated-dependencies: - dependency-name: puppeteer dependency-version: 25.0.3 dependency-type: direct:development update-type: version-update:semver-major dependency-group: puppeteer ... Signed-off-by: dependabot[bot] <support@github.com>
|
@copilot review nevware21/ts-utils#559 and apply the same changes to unblock puppeteer |
Applied the same fix from nevware21/ts-utils#559 to both In puppeteer v25, Commit: fix: update karma configs for puppeteer v25 async executablePath |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #218 +/- ##
=======================================
Coverage 89.86% 89.86%
=======================================
Files 23 23
Lines 513 513
Branches 138 138
=======================================
Hits 461 461
Misses 52 52 🚀 New features to boost your workflow:
|
nevware21-bot
left a comment
There was a problem hiding this comment.
Approved by nevware21-bot
Bumps the puppeteer group with 1 update: puppeteer.
Updates
puppeteerfrom 24.43.1 to 25.0.3Additional fix: Puppeteer v25 changed
executablePath()to return aPromiseinstead of a synchronous value. Updatedcore/karma.browser.conf.jsandcore/karma.worker.conf.jsto resolve the executable path synchronously via a child subprocess, keeping Karma configs synchronous and unblocking the upgrade.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.