chore(deps): update dependency puppeteer to v25.8.0 - #4048
Merged
Conversation
Re-applies the renovate bump from the pre-merge master. Requires a pnpm dedupe so fingerprint-injector resolves against the same puppeteer-core instance instead of a stale 25.3.0 peer snapshot in the lockfile.
B4nan
added
t-tooling
barjin
approved these changes
Aug 19, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Re-applies the puppeteer 25.8.0 bump that renovate landed on the pre-merge master (the v4 merge brought back the old 25.3.0 pin). The version change alone is not enough: the lockfile keeps a stale
fingerprint-injector(puppeteer@25.3.0)peer instance around, and the duplicatedpuppeteer-coretypes breaktsc-check-testswith 82 errors. Apnpm dedupecollapses the graph back to a single instance.