Bump puppeteer-core to ^20.8.2 to patch vulnerability #459
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tw4l
changed the title
Resolves #456
tw4l
force-pushed
the
puppeteer-core-upgrade
branch
from
ead6782
to
dfb2af1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #456
We'll want to do the same for the 1.0.0-beta branch.
It looks like bumping straight to the latest major release of puppeteer-core (21.x.x) resulted in some test failures around text extraction and blockrules, so I'm just bumping to a version that contains the patch for now until we have more time to investigate.