Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions playwright/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -8,14 +8,14 @@
"test:debug": "playwright test --debug"
},
"devDependencies": {
"@playwright/test": "1.42.1",
"@playwright/test": "1.56.0",
"eslint": "8.57.0",
"eslint-config-standard": "17.1.0",
"eslint-plugin-import": "2.29.1",
"eslint-plugin-n": "16.6.2",
"eslint-plugin-node": "11.1.0",
"eslint-plugin-promise": "6.1.1",
"npm-check-updates": "16.14.18"
"npm-check-updates": "17.0.0"
},
Comment on lines 10 to 19
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

This pull request updates two development dependencies, including a major version bump for npm-check-updates (16.x to 17.x). While this is important for security, there are two key concerns:

  1. Missing package-lock.json update: The package-lock.json file has not been updated to reflect the version changes in package.json. This is critical because it can lead to inconsistent dependency trees across different environments. Please run npm install to generate the updated package-lock.json and commit it to this PR.

  2. Potential Breaking Changes: The Snyk report indicates this is a breaking change (isBreakingChange:true). Major version updates, like the one for npm-check-updates, often include breaking changes. The update for @playwright/test is also a large jump across minor versions. It is highly recommended to:

    • Review the release notes for both packages to understand the changes.
    • Thoroughly test the project to ensure that these updates do not break your tests or development workflows.

"dependencies": {
"@faker-js/faker": "8.4.1",
Expand Down
Loading