Skip to content

Ab#113056#18

Merged
sebastianchristopher merged 5 commits intomasterfrom
AB#113056
Feb 6, 2026
Merged

Ab#113056#18
sebastianchristopher merged 5 commits intomasterfrom
AB#113056

Conversation

@sebastianchristopher
Copy link
Contributor

Due to microsoft/playwright#39172 we just want to make sure we're not pulling in the latest version for now.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR constrains the Playwright peer dependency version to avoid a bug introduced in Playwright 1.58.0 that causes duplicate test title errors (referenced issue: microsoft/playwright#39172). The constraint >=1.36.0 <1.58.0 allows versions from 1.36.0 up to (but not including) 1.58.0.

Changes:

  • Updated peer dependency constraint for @playwright/test from ^1.55.1 to >=1.36.0 <1.58.0 in both package.json and package-lock.json
  • Added documentation in README.md explaining the version constraint and the reason for it

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.

File Description
package.json Updated peerDependencies to constrain Playwright version to <1.58.0
package-lock.json Updated peerDependencies to match package.json constraint
README.md Added NOTE explaining the Playwright version constraint and workaround guidance

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

README.md Outdated
```

> [!NOTE]
> Playwright 1.58.0.0 introduced a [bug](https://github.com/microsoft/playwright/issues/39172) that causes duplicate test title errors. The latest release of this library version locks Playwright to <1.58.0 to avoid this issue, but if you are using a later version of Playwright in your project, you may need to adjust the version in your `package.json` to avoid conflicts.
Copy link

Copilot AI Feb 6, 2026

Choose a reason for hiding this comment

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

The phrasing "The latest release of this library version locks" is awkward and unclear. Consider rephrasing to "This library version locks" or "This version of the library constrains" for better clarity.

Suggested change
> Playwright 1.58.0.0 introduced a [bug](https://github.com/microsoft/playwright/issues/39172) that causes duplicate test title errors. The latest release of this library version locks Playwright to <1.58.0 to avoid this issue, but if you are using a later version of Playwright in your project, you may need to adjust the version in your `package.json` to avoid conflicts.
> Playwright 1.58.0.0 introduced a [bug](https://github.com/microsoft/playwright/issues/39172) that causes duplicate test title errors. This version of the library locks Playwright to <1.58.0 to avoid this issue, but if you are using a later version of Playwright in your project, you may need to adjust the version in your `package.json` to avoid conflicts.

Copilot uses AI. Check for mistakes.
sebastianchristopher and others added 2 commits February 6, 2026 16:07
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Updated note about Playwright version constraint for clarity.
Copy link
Member

@buckett buckett left a comment

Choose a reason for hiding this comment

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

Nice.

Copy link
Contributor

@lardo-de-arnaud lardo-de-arnaud left a comment

Choose a reason for hiding this comment

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

straight into the back of the net by the young lad Johnson.

@sebastianchristopher sebastianchristopher merged commit a6028e5 into master Feb 6, 2026
1 check passed
@sebastianchristopher sebastianchristopher deleted the AB#113056 branch February 6, 2026 16:20
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.

4 participants