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

[dependabot]

Bumps @playwright/test from 1.59.0-alpha-2026-03-01 to 1.59.0-alpha-1773706743000.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

Summary by cubic

Upgrade @playwright/test to 1.59.0-alpha-1773706743000 to pick up the latest fixes and improvements in our backend tests. Dev-only change with no production impact.

• Dependencies
  • Bumped @playwright/test in apps/backend/package.json; refreshed lockfile.

^{Written for commit 5f60f13. Summary will update on new commits.}

[dependabot]

Assignees

The following users could not be added as assignees: TomCo, Tomco. Either they do not exist or they do not have the correct permissions to be added as an assignee.

Labels

The following labels could not be found: auto-update, dependencies, frontend. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
tc-dynamics	Ready	Preview, Comment	Mar 17, 2026 6:19am

[cubic-dev-ai]

No issues found across 2 files

[greptile-apps]

Greptile Summary

This PR is a Dependabot bump of the @playwright/test dev dependency from a date-based alpha (1.59.0-alpha-2026-03-16 in apps/backend/package.json) to a timestamp-based alpha (1.59.0-alpha-1773706743000). Unfortunately the package-lock.json is not properly regenerated, leaving the resolved version and workspace specifier pointing at an older alpha that does not satisfy the new version range.

Key issues found:

• The package-lock.json workspace devDependencies for apps/backend was set to ^1.59.0-alpha-2026-03-01 instead of the new ^1.59.0-alpha-1773706743000, and the resolved entry for apps/backend/node_modules/@playwright/test remains at 1.59.0-alpha-2026-03-01. Because semver pre-release ordering means 1.59.0-alpha-2026-03-01 < 1.59.0-alpha-1773706743000, the lock file does not satisfy the new range and npm ci will fail.
• The PR title/description states the previous version was 1.59.0-alpha-2026-03-01, but apps/backend/package.json was actually at 1.59.0-alpha-2026-03-16 before this change, suggesting Dependabot generated the PR against a stale base.

Recommendation: Re-run npm install (or trigger a Dependabot rebase via @dependabot rebase) so that package-lock.json is regenerated and the new resolved package entry is correctly recorded.

Confidence Score: 1/5

• Not safe to merge — the lock file is inconsistent with package.json and will cause npm ci to fail in CI/CD.
• The package-lock.json resolved entry for @playwright/test was not updated to the new version, and the workspace specifier in the lock file does not match package.json. Any install using npm ci will error out. This is a blocking issue.
• package-lock.json needs to be fully regenerated to include the resolved 1.59.0-alpha-1773706743000 package entry.

Important Files Changed

Filename	Overview
apps/backend/package.json	Version range updated to ^1.59.0-alpha-1773706743000, but the corresponding lock file is not updated to resolve this new version, causing npm ci to fail.
package-lock.json	Lock file is inconsistently updated: the workspace devDependencies specifier reverts to ^1.59.0-alpha-2026-03-01 (not the new version) and the resolved entry for @playwright/test remains at 1.59.0-alpha-2026-03-01, so it does not satisfy the new ^1.59.0-alpha-1773706743000 range in package.json.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["package.json: @playwright/test ^1.59.0-alpha-1773706743000"] --> B{Does lock file satisfy range?}
    B --> C["package-lock.json resolved: 1.59.0-alpha-2026-03-01"]
    C --> D["alpha-2026-03-01 is LESS THAN alpha-1773706743000"]
    D --> E["Range NOT satisfied - npm ci FAILS"]
    B --> F["Expected: lock resolves 1.59.0-alpha-1773706743000"]
    F --> G["Range satisfied - npm ci succeeds"]

Loading

_{Last reviewed commit: 5f60f13}

[greptile-apps]

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.