Skip to content

chore(deps-dev): bump @playwright/test from 1.59.0-alpha-2026-03-01 to 1.59.0-alpha-1773706743000 #201

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
github-actions merged 1 commit into from
Mar 17, 2026
Merged

chore(deps-dev): bump @playwright/test from 1.59.0-alpha-2026-03-01 to 1.59.0-alpha-1773706743000 #201

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion apps/backend/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@
"winston": "^3.19.0"
},
"devDependencies": {
"@playwright/test": "^1.59.0-alpha-2026-03-16",
"@playwright/test": "^1.59.0-alpha-1773706743000",
Copy link
Contributor

@greptile-apps greptile-apps bot Mar 17, 2026

Choose a reason for hiding this comment

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

P0 Incomplete package-lock.json update

apps/backend/package.json now specifies ^1.59.0-alpha-1773706743000, but package-lock.json is not properly updated to match. Two issues exist in the lock file:

  1. The workspace devDependencies entry (line 246) still reflects ^1.59.0-alpha-2026-03-01 instead of the new ^1.59.0-alpha-1773706743000.
  2. The resolved package at apps/backend/node_modules/@playwright/test is still 1.59.0-alpha-2026-03-01 — the new version is never fetched or locked.

In semver pre-release ordering, alpha-1773706743000 (numeric identifier 1773706743000) is greater than alpha-2026-03-01 (identifier 2026). This means 1.59.0-alpha-2026-03-01 does not satisfy the ^1.59.0-alpha-1773706743000 range, so npm ci will fail with an "Invalid: lock file's version ... does not satisfy ... package.json's version" error.

The lock file needs to be regenerated (or manually corrected) so the resolved entry matches the new version.

"@types/compression": "^1.8.1",
"@types/cookie-parser": "^1.4.10",
"@types/cors": "^2.8.19",
Expand Down
2 changes: 1 addition & 1 deletion package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading