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

[dependabot]

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

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-1773608981000 to keep e2e tests current and CI stable. Dev-only change with no production impact.

• Dependencies
  • Bumped @playwright/test in apps/backend.
  • Regenerated package-lock.json with incidental @commitlint/* patch updates.

^{Written for commit e4371cc. 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 16, 2026 6:22am

[cubic-dev-ai]

No issues found across 2 files

[greptile-apps]

Greptile Summary

Dependabot PR to bump @playwright/test from an alpha pre-release to a newer alpha (1.59.0-alpha-1773608981000). The package.json update looks correct, but the package-lock.json is out of sync — its specifier and resolved version still point to the older 1.59.0-alpha-2026-03-01 alpha rather than the new 1773608981000 version. The lock file also includes unrelated @commitlint minor bumps (20.4.4 → 20.5.0).

• Version mismatch: package.json specifies ^1.59.0-alpha-1773608981000 but package-lock.json resolves 1.59.0-alpha-2026-03-01 — the lock file needs to be regenerated.
• Unrelated changes: Several @commitlint packages were bumped from 20.4.4 to 20.5.0 in the lock file, which is not covered by the PR description.

Confidence Score: 2/5

• The lock file is out of sync with package.json, so installs may not resolve the intended version.
• Score of 2 reflects a version mismatch between package.json and package-lock.json for the primary dependency being bumped. While this only affects a dev dependency (Playwright) and won't impact production, it means CI/CD may not install the intended version, and fresh installs will behave differently from locked installs.
• Pay close attention to package-lock.json — the resolved @playwright/test version doesn't match the package.json specifier.

Important Files Changed

Filename	Overview
apps/backend/package.json	Updates @playwright/test specifier from ^1.59.0-alpha-2026-03-15 to ^1.59.0-alpha-1773608981000. Change itself is straightforward but the version doesn't match what the lock file resolved.
package-lock.json	Lock file specifier and resolved version are out of sync with package.json. Also includes unrelated @commitlint bumps (20.4.4 → 20.5.0) that aren't mentioned in the PR title.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["package.json specifier<br/>^1.59.0-alpha-1773608981000"] --> B{"npm ci"}
    A --> C{"npm install (fresh)"}
    D["package-lock.json resolved<br/>1.59.0-alpha-2026-03-01"] --> B
    B --> E["Installs 2026-03-01 ❌<br/>(ignores package.json intent)"]
    C --> F["Resolves 1773608981000 from registry<br/>(inconsistent with lock)"]
    style E fill:#f96,stroke:#333
    style F fill:#ff9,stroke:#333

Loading

_{Last reviewed commit: e4371cc}

[greptile-apps]

package-lock.json out of sync with package.json

The package.json specifier was updated to ^1.59.0-alpha-1773608981000, but the lock file's specifier was changed to ^1.59.0-alpha-2026-03-01 (a different, older alpha tag). Additionally, the resolved version in the lock file is 1.59.0-alpha-2026-03-01, not 1.59.0-alpha-1773608981000.

This mismatch means:

• npm ci will use the lock file's resolved 2026-03-01 version (ignoring the package.json intent).
• npm install in a fresh checkout will resolve ^1.59.0-alpha-1773608981000 from the registry, which may differ from what's locked here.

This lock file should be regenerated so the specifier and resolved version both reflect 1.59.0-alpha-1773608981000.