image-sequencer icon indicating copy to clipboard operation
image-sequencer copied to clipboard
verified publisher icon publiclab

Bump puppeteer from 1.19.0 to 13.0.1

Open dependabot[bot] opened this issue 3 years ago • 6 comments

Bumps puppeteer from 1.19.0 to 13.0.1.

Release notes

Sourced from puppeteer's releases.

13.0.1

Bug Fixes

  • disable a test failing on Firefox (#7846) (36207c5)
  • make sure ElementHandle.waitForSelector is evaluated in the right context (#7843) (8d8e874)
  • predicate arguments for waitForFunction (#7845) (1c44551), closes #7836

13.0.0

⚠ BREAKING CHANGES

  • typo in 'already-handled' constant of the request interception API (#7813)

Features

  • expose HTTPRequest intercept resolution state and clarify docs (#7796) (dc23b75)
  • implement Element.waitForSelector (#7825) (c034294)

Bug Fixes

12.0.1

Bug Fixes

  • handle extraInfo events even if event.hasExtraInfo === false (#7808) (6ee2feb), closes #7805

12.0.0

⚠ BREAKING CHANGES

  • chromium: roll to Chromium 97.0.4692.0 (r938248)

Features

  • chromium: roll to Chromium 97.0.4692.0 (r938248) (ac162c5), closes #7458
  • support for custom user data (profile) directory for Firefox (#7684) (790c7a0)

Bug Fixes

  • ariaqueryhandler: allow single quotes in aria attribute selector (#7750) (b0319ec), closes #7721
  • clearer jsdoc for behavior of headless when devtools is true (#7748) (9f9b4ed)
  • null check for frame in FrameManager (#7773) (23ee295), closes #7749
  • only kill the process when there is no browser instance available (#7762) (51e6169), closes #7668
  • parse statusText from the extraInfo event (#7798) (a26b12b), closes #7458
  • try to remove the temporary user data directory after the process has been killed (#7761) (fc94a28)

... (truncated)

Changelog

Sourced from puppeteer's changelog.

13.0.1 (2021-12-22)

Bug Fixes

  • disable a test failing on Firefox (#7846) (36207c5)
  • make sure ElementHandle.waitForSelector is evaluated in the right context (#7843) (8d8e874)
  • predicate arguments for waitForFunction (#7845) (1c44551), closes #7836

13.0.0 (2021-12-10)

⚠ BREAKING CHANGES

  • typo in 'already-handled' constant of the request interception API (#7813)

Features

  • expose HTTPRequest intercept resolution state and clarify docs (#7796) (dc23b75)
  • implement Element.waitForSelector (#7825) (c034294)

Bug Fixes

12.0.1 (2021-11-29)

Bug Fixes

  • handle extraInfo events even if event.hasExtraInfo === false (#7808) (6ee2feb), closes #7805

12.0.0 (2021-11-26)

⚠ BREAKING CHANGES

  • chromium: roll to Chromium 97.0.4692.0 (r938248)

Features

  • chromium: roll to Chromium 97.0.4692.0 (r938248) (ac162c5), closes #7458
  • support for custom user data (profile) directory for Firefox (#7684) (790c7a0)

Bug Fixes

... (truncated)

Commits
  • 71cef32 chore(release): mark v13.0.1 (#7865)
  • 8d8e874 fix: make sure ElementHandle.waitForSelector is evaluated in the right contex...
  • 1c44551 fix: predicate arguments for waitForFunction (#7845)
  • 36207c5 fix: disable a test failing on Firefox (#7846)
  • 3e3a90b docs: fix typo (#7839)
  • acdc67b chore: bump version to v13.0.0-post (#7833)
  • d0cb9e2 chore(release): mark v13.0.0 (#7832)
  • 02c9af6 fix(types): revert "feat(typescript): allow using puppeteer without dom lib"
  • 8242422 fix!: typo in 'already-handled' constant of the request interception API (#7813)
  • 71cc1b9 refactor: remove unused promise (#7830)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by google-wombot, a new releaser for puppeteer since your current version.


Dependabot compatibility score

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 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[bot] avatar Dec 22 '21 08:12 dependabot[bot]

gitpod-io[bot] avatar Dec 22 '21 08:12 gitpod-io[bot]

We could be looking at this issue running multiple Puppeteers in parallel...?

https://github.com/smooth-code/jest-puppeteer/tree/master#running-puppeteer-in-ci-environments

Running puppeteer in CI environments

Most continuous integration platforms limit the number of threads one can use. If you have more than one test suite running puppeteer chances are that your test will timeout. This is because jest will try to run puppeteer in parallel and the CI platform won't be able to handle all the parallel jobs in time. A fix to this is to run your test serially when in a CI environment. Users have discovered that running test serially in such environments can render up to 50% of performance gains.

This can be achieved through the CLI by running:

jest --runInBand

Alternatively, you can set jest to use as a max number of workers the amount that your CI environment supports:

jest --maxWorkers=2

jywarren avatar Dec 22 '21 23:12 jywarren

Pretty stuck here. Let's try running it on other versions of puppeteer in GitPod or in another PR?

jywarren avatar Dec 28 '21 18:12 jywarren

Editor project has: jest-puppeteer "version": "4.4.0", while here we're at v6.0.0+

Could there be a jest-puppeteer/jest version compatibility issue?

jywarren avatar Dec 28 '21 18:12 jywarren

Yes -- look at https://github.com/publiclab/image-sequencer/pull/1839#issuecomment-827855074

jywarren avatar Dec 28 '21 18:12 jywarren

A newer version of puppeteer exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

dependabot[bot] avatar Jan 18 '22 08:01 dependabot[bot]