Skip to content

[Snyk] Upgrade playwright from 1.53.1 to 1.53.2#159

Open
anubissbe wants to merge 1 commit intomainfrom
snyk-upgrade-1815ebed5e2546f9d5ca3c45ff97110c
Open

[Snyk] Upgrade playwright from 1.53.1 to 1.53.2#159
anubissbe wants to merge 1 commit intomainfrom
snyk-upgrade-1815ebed5e2546f9d5ca3c45ff97110c

Conversation

@anubissbe
Copy link
Copy Markdown
Owner

@anubissbe anubissbe commented Jul 23, 2025

snyk-top-banner

Snyk has created this PR to upgrade playwright from 1.53.1 to 1.53.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.

  • The recommended version was released 23 days ago.

Release notes
Package name: playwright
  • 1.53.2 - 2025-06-30

    Highlights

    #36317 - [Regression]: Merging pre-1.53 blob reports loses attachments
    #36357 - [Regression (Chromium)]: CDP missing trailing slash
    #36292 - [Bug (MSEdge)]: Edge fails to launch when using msRelaunchNoCompatLayer

    Browser Versions

    • Chromium 138.0.7204.23
    • Mozilla Firefox 139.0
    • WebKit 18.5

    This version was also tested against the following stable channels:

    • Google Chrome 137
    • Microsoft Edge 137
  • 1.53.2-beta-1751304415000 - 2025-06-30
  • 1.53.1 - 2025-06-18

    Highlights

    #36339 - [Regression]: Click can fail when scrolling required
    #36307 - [Regression (Chromium)]: Under some scenarios filling a textarea doesn't fill
    #36294 - [Regression (Firefox)]: setViewportSize times out
    #36350 - [Fix]: Display HTTP method for fetch trace entries

    Browser Versions

    • Chromium 138.0.7204.23
    • Mozilla Firefox 139.0
    • WebKit 18.5

    This version was also tested against the following stable channels:

    • Google Chrome 137
    • Microsoft Edge 137
from playwright GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Summary by Sourcery

Chores:

  • Bump Playwright from ^1.53.1 to ^1.53.2

Description by Korbit AI

What change is being made?

Upgrade the playwright dependency from version 1.53.1 to 1.53.2 in the package.json.

Why are these changes being made?

This update includes minor fixes and improvements provided in playwright version 1.53.2, ensuring the project benefits from the latest enhancements and potential bug fixes without affecting backward compatibility.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

Snyk has created this PR to upgrade playwright from 1.53.1 to 1.53.2.

See this package in npm:
playwright

See this project in Snyk:
https://app.snyk.io/org/anubissbe/project/72057889-945c-48e5-b9b6-a5b9221ec2b1?utm_source=github&utm_medium=referral&page=upgrade-pr
@sourcery-ai
Copy link
Copy Markdown

sourcery-ai bot commented Jul 23, 2025

Reviewer's Guide

Updated the Playwright dependency from 1.53.1 to 1.53.2 by adjusting the version string in package.json to leverage the latest fixes and regression patches.

File-Level Changes

Change Details Files
Dependency version bump
  • Updated Playwright version in dependencies
package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@anubissbe
Copy link
Copy Markdown
Owner Author

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

Copy link
Copy Markdown

@korbit-ai korbit-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've completed my review and didn't find any issues... but I did find this owl.

 ,_,
(.,.)
(   )
-"-"---

Check out our docs on how you can make Korbit work best for you and your team.

Loving Korbit!? Share us on LinkedIn Reddit and X

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants