Bump playwright and @playwright/test in /zeppelin-web-angular#5107
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Bump playwright and @playwright/test in /zeppelin-web-angular#5107dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [playwright](https://github.com/microsoft/playwright) to 1.56.1 and updates ancestor dependency [@playwright/test](https://github.com/microsoft/playwright). These dependencies need to be updated together. Updates `playwright` from 1.53.2 to 1.56.1 - [Release notes](https://github.com/microsoft/playwright/releases) - [Commits](microsoft/playwright@v1.53.2...v1.56.1) Updates `@playwright/test` from 1.53.2 to 1.56.1 - [Release notes](https://github.com/microsoft/playwright/releases) - [Commits](microsoft/playwright@v1.53.2...v1.56.1) --- updated-dependencies: - dependency-name: playwright dependency-version: 1.56.1 dependency-type: indirect - dependency-name: "@playwright/test" dependency-version: 1.56.1 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
tbonelee
pushed a commit
that referenced
this pull request
Oct 24, 2025
…g Playwright browsers ### What is this PR for? #5107 https://github.com/apache/zeppelin/actions/runs/18662031473/job/53204596550?pr=5107 In the Playwright E2E tests of the above bump PR, the following issue occurred: ``` Error: browserType.launch: Executable doesn't exist at /home/runner/.cache/ms-playwright/webkit-2215/pw_run.sh ``` This issue seems to be caused by the Playwright browser installation step being version-locked in `zeppelin-web-angular/pom.xml`'s playwright-install execution. Instead of managing it in `pom.xml`, it would be better to add it to the `postinstall` script in `zeppelin-web-angular/package.json`, so that Playwright browsers are automatically installed when running `npm install`, either in CI and on a local environment. This PR addresses that change. 61ff629 Including the CI caching procedure as above, it seems optimized as previous approach(pom.xml). ### What type of PR is it? Improvement ### Todos ### What is the Jira issue? ZEPPELIN-6370 ### How should this be tested? ### Screenshots (if appropriate) ### Questions: * Does the license files need to update? No * Is there breaking changes for older versions? No * Does this needs documentation? No Closes #5108 from dididy/e2e/upgrade-playwright. Signed-off-by: ChanHo Lee <chanholee@apache.org>
tbonelee
pushed a commit
that referenced
this pull request
Oct 24, 2025
…g Playwright browsers ### What is this PR for? #5107 https://github.com/apache/zeppelin/actions/runs/18662031473/job/53204596550?pr=5107 In the Playwright E2E tests of the above bump PR, the following issue occurred: ``` Error: browserType.launch: Executable doesn't exist at /home/runner/.cache/ms-playwright/webkit-2215/pw_run.sh ``` This issue seems to be caused by the Playwright browser installation step being version-locked in `zeppelin-web-angular/pom.xml`'s playwright-install execution. Instead of managing it in `pom.xml`, it would be better to add it to the `postinstall` script in `zeppelin-web-angular/package.json`, so that Playwright browsers are automatically installed when running `npm install`, either in CI and on a local environment. This PR addresses that change. 61ff629 Including the CI caching procedure as above, it seems optimized as previous approach(pom.xml). ### What type of PR is it? Improvement ### Todos ### What is the Jira issue? ZEPPELIN-6370 ### How should this be tested? ### Screenshots (if appropriate) ### Questions: * Does the license files need to update? No * Is there breaking changes for older versions? No * Does this needs documentation? No Closes #5108 from dididy/e2e/upgrade-playwright. Signed-off-by: ChanHo Lee <chanholee@apache.org> (cherry picked from commit 0a768bc) Signed-off-by: ChanHo Lee <chanholee@apache.org>
Contributor
Author
|
Looks like these dependencies are up-to-date now, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/zeppelin-web-angular/multi-a50d7f32cf
branch
voidmatcha
added a commit
to voidmatcha/zeppelin
that referenced
this pull request
Oct 26, 2025
…g Playwright browsers apache#5107 https://github.com/apache/zeppelin/actions/runs/18662031473/job/53204596550?pr=5107 In the Playwright E2E tests of the above bump PR, the following issue occurred: ``` Error: browserType.launch: Executable doesn't exist at /home/runner/.cache/ms-playwright/webkit-2215/pw_run.sh ``` This issue seems to be caused by the Playwright browser installation step being version-locked in `zeppelin-web-angular/pom.xml`'s playwright-install execution. Instead of managing it in `pom.xml`, it would be better to add it to the `postinstall` script in `zeppelin-web-angular/package.json`, so that Playwright browsers are automatically installed when running `npm install`, either in CI and on a local environment. This PR addresses that change. 61ff629 Including the CI caching procedure as above, it seems optimized as previous approach(pom.xml). Improvement ZEPPELIN-6370 * Does the license files need to update? No * Is there breaking changes for older versions? No * Does this needs documentation? No Closes apache#5108 from dididy/e2e/upgrade-playwright. Signed-off-by: ChanHo Lee <chanholee@apache.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps playwright to 1.56.1 and updates ancestor dependency @playwright/test. These dependencies need to be updated together.
Updates
playwrightfrom 1.53.2 to 1.56.1Release notes
Sourced from playwright's releases.
... (truncated)
Commits
54c7115chore: revert "minimal vscode version notice" (#37892)7d45eb3chore: mark v1.56.1 (#37784)e6ef697cherry-pick(#37871): chore: allow local-network-access permission in chromium932542ccherry-pick(#37891): fix(agents): remove workspaceFolder ref from vscode mcp0662dd2cherry-pick(#37759): chore: rename agents to test agents919549echerry-pick(#37758): docs: mention VS Code insiders in the agents docse593c64cherry-pick(#37757): chore(mcp): fallback to cwd when resolving test configa8a6e10cherry-pick(#37755): chore(mcp): minimal vscode version noticef36b2eecherry-pick(#37731): docs: add agents video to agents page (#37733)b6af258cherry-pick(#37727): devops: fix NPM release step (#37728)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for playwright since your current version.
Updates
@playwright/testfrom 1.53.2 to 1.56.1Release notes
Sourced from
@playwright/test's releases.... (truncated)
Commits
54c7115chore: revert "minimal vscode version notice" (#37892)7d45eb3chore: mark v1.56.1 (#37784)e6ef697cherry-pick(#37871): chore: allow local-network-access permission in chromium932542ccherry-pick(#37891): fix(agents): remove workspaceFolder ref from vscode mcp0662dd2cherry-pick(#37759): chore: rename agents to test agents919549echerry-pick(#37758): docs: mention VS Code insiders in the agents docse593c64cherry-pick(#37757): chore(mcp): fallback to cwd when resolving test configa8a6e10cherry-pick(#37755): chore(mcp): minimal vscode version noticef36b2eecherry-pick(#37731): docs: add agents video to agents page (#37733)b6af258cherry-pick(#37727): devops: fix NPM release step (#37728)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@playwright/testsince your current version.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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.