deps: bump @playwright/test from 1.46.1 to 1.61.1 - #37
Merged
github-actions[bot] merged 2 commits intoAug 14, 2026
Conversation
Bumps [@playwright/test](https://github.com/microsoft/playwright) from 1.46.1 to 1.61.1. - [Release notes](https://github.com/microsoft/playwright/releases) - [Commits](microsoft/playwright@v1.46.1...v1.61.1) --- updated-dependencies: - dependency-name: "@playwright/test" dependency-version: 1.61.1 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
github-actions
Bot
deleted the
dependabot/npm_and_yarn/playwright/test-1.61.1
branch
August 14, 2026 00:33
github-actions Bot
pushed a commit
that referenced
this pull request
Aug 14, 2026
#75) The sweep merges a PR only if it "has at least one check". Correct — but GitHub never retroactively runs workflows, so every PR opened before this repo gained its CI floor (2026-08-05/08-07) has zero checks, cannot gain any on its own, and parks permanently. The script already spotted this and only warned about it; warning does not move them. Worse, they report as CLEAN, which reads as "ready to merge" and actually means "nothing ever objected". Waking solon's five showed what CLEAN was hiding: lucide-react, @noble/hashes and @noble/secp256k1 all fail verify — secp256k1 v3 removes hmacSha256Sync, randomPrivateKey, sig.recovery, toCompactRawBytes and Signature.fromCompact, which is the Bitcoin message signing path. Only @playwright/test was genuinely green (merged, #37). So the sweep now pushes such branches via update-branch, which fires pull_request:synchronize and produces real checks. This grants nothing: a woken PR still has to go green to merge, and a red one parks exactly where it already was — it only replaces "no evidence" with evidence. Capped at WAKE_MAX_PER_SWEEP (3) so a backlog does not stampede the runners; waking does not touch the base, so the one-car-per-sweep rule does not apply. Conflicted branches cannot be updated and are left to the existing CONFLICTING report instead of burning a slot. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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/test from 1.46.1 to 1.61.1.
Release notes
Sourced from @playwright/test's releases.
... (truncated)
Commits
39e3553cherry-pick(#41399): fix(test): load require-reached files as commonjs in syn...4328122chore: mark v1.61.1 (#41404)2c29a94fix(tracing): stop recording websocket frames outside of chunks (#41398)4324b19cherry-pick(#41367): fix(test): keep builtin expect matchers on base extend041e7e3cherry-pick(#41364): fix(har):WebSocketmessage timestamps should be in mi...b8a0fc3cherry-pick(#41309, #43149): Revert "fix(firefox): treat `navigationCommitted...b5a3175cherry-pick(#41319): fix(loader): support other node versionsd4724a9cherry-pick(#41290): feat(docker): add Ubuntu 26.04 (Resolute Raccoon) image1cc5a90cherry-pick(#41295): chore: PLAYWRIGHT_TRACING_NO_WEBSOCKET_FRAMES and PLAYWR...a6772bdcherry-pick(#41280): Revert "fix(trace-viewer): add keyboard navigation to `N...Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@playwright/testsince your current version.You can trigger a rebase of this PR 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 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)