-
-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump puppeteer from 1.9.0 to 22.7.0 #1013
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@dependabot rebase |
Bumps [puppeteer](https://github.com/puppeteer/puppeteer) from 1.9.0 to 22.7.0. - [Release notes](https://github.com/puppeteer/puppeteer/releases) - [Changelog](https://github.com/puppeteer/puppeteer/blob/main/release-please-config.json) - [Commits](puppeteer/puppeteer@v1.9.0...puppeteer-v22.7.0) --- updated-dependencies: - dependency-name: puppeteer dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
a5f7d5b
to
d918b67
Compare
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ran tests on this branch to see if it is possible to update puppeteer in isolation, but tests do not pass:
dkatz@dkatz-VirtualBox:~/universalviewer$ npm test
> [email protected] test
> jest
FAIL src/Utils.spec.ts
● Test suite failed to run
TypeError: page.removeListener is not a function
at PuppeteerEnvironment.teardown (node_modules/jest-environment-puppeteer/lib/PuppeteerEnvironment.js:134:12)
at Generator.throw (<anonymous>)
FAIL __tests__/test.js
● Test suite failed to run
TypeError: page.removeListener is not a function
at PuppeteerEnvironment.teardown (node_modules/jest-environment-puppeteer/lib/PuppeteerEnvironment.js:134:12)
at Generator.throw (<anonymous>)
FAIL __tests__/configuration_options.js
● Test suite failed to run
TypeError: page.removeListener is not a function
at PuppeteerEnvironment.teardown (node_modules/jest-environment-puppeteer/lib/PuppeteerEnvironment.js:134:12)
at Generator.throw (<anonymous>)
FAIL src/content-handlers/iiif/PubSub.spec.ts
● Test suite failed to run
TypeError: page.removeListener is not a function
at PuppeteerEnvironment.teardown (node_modules/jest-environment-puppeteer/lib/PuppeteerEnvironment.js:134:12)
at Generator.throw (<anonymous>)
FAIL src/content-handlers/iiif/modules/uv-shared-module/XYWHFragment.spec.ts
● Test suite failed to run
TypeError: page.removeListener is not a function
at PuppeteerEnvironment.teardown (node_modules/jest-environment-puppeteer/lib/PuppeteerEnvironment.js:134:12)
at Generator.throw (<anonymous>)
Test Suites: 5 failed, 5 total
Tests: 0 total
Snapshots: 0 total
Time: 1.871s
Ran all test suites.
We should not merge this as-is; instead, we should figure out how to finish the work started in #984.
Superseded by #1015. |
Bumps puppeteer from 1.9.0 to 22.7.0.
Release notes
Sourced from puppeteer's releases.
... (truncated)
Commits
02cf1c7
chore: release main (#12280)f239130
chore: don't detach CdpSession (#12154)ed9d7dd
feat: roll to Chrome 124.0.6367.60 (r1274542) (#12305)2968f21
docs: setup a redirect for network page (#12303)c7db415
chore(deps-dev): Bump the dev-dependencies group with 8 updates (#12297)f90bdbc
chore(deps-dev): Bump@swc/core
from 1.4.13 to 1.4.16 in /website in the all ...7a40845
chore(deps): Bump the all group with 5 updates (#12299)29e33df
refactor: remove EventSubscription (#12277)9a17ec3
fix(performance): cache isolatedHandle (#12150)3b70667
docs: update the extensions guide (#12290)Maintainer changes
This version was pushed to npm by google-wombot, 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)