deps: bump @playwright/cli from 0.1.14 to 0.1.15#43196
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
|
Hey A couple of things to address before this is ready:
When ready, here's a prompt you can assign to complete the work:
|
|
✅ Design Decision Gate 🏗️ completed the design decision gate check. No ADR enforcement needed: PR does not have the 'implementation' label and has ≤100 new lines of code in business logic directories (only 3 additions detected). |
|
✅ Test Quality Sentinel completed test quality analysis. |
|
🧠 Matt Pocock Skills Reviewer has completed the skills-based review. ✅ |
|
✅ PR Code Quality Reviewer completed the code quality review. |
There was a problem hiding this comment.
Pull request overview
Patch version bump of the pinned @playwright/cli version used by gh-aw when Playwright is run in cli mode, along with updating the associated cooldown-guard test metadata.
Changes:
- Bump
DefaultPlaywrightCLIVersionfrom0.1.14to0.1.15. - Update
TestDefaultPlaywrightCLIVersionOutsideCooldownWindowto expect0.1.15and record the v0.1.15 npm publish timestamp.
Show a summary per file
| File | Description |
|---|---|
| pkg/constants/version_constants.go | Updates the default pinned Playwright CLI npm version to 0.1.15. |
| pkg/constants/version_constants_test.go | Refreshes cooldown-guard test metadata (expected version + publish timestamp) for 0.1.15. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Low
| // DefaultPlaywrightCLIVersion is the default version of the @playwright/cli package. | ||
| // Used when tools.playwright.mode is "cli" to install the CLI tool instead of the MCP server. | ||
| // Keep this version outside the default 3-day npm release-age cooldown window enforced by | ||
| // generated Playwright CLI install steps. See TestDefaultPlaywrightCLIVersionOutsideCooldownWindow. | ||
| const DefaultPlaywrightCLIVersion Version = "0.1.14" | ||
| const DefaultPlaywrightCLIVersion Version = "0.1.15" |
There was a problem hiding this comment.
Skills-Based Review 🧠
Applied /tdd — changes are correct and well-documented. Approving.
📋 Key Themes & Highlights
Key Themes
- Routine patch bump:
DefaultPlaywrightCLIVersion0.1.14→0.1.15, low risk. - Test correctly refreshed:
expectedVersionandpublishedAtRFC3339updated to match npm publish timestamp for v0.1.15 (2026-06-30T14:53:08.941Z). - Timing note: The 72-hour cooldown expires at
2026-07-03T14:53:08Z. The PR description calls this out explicitly — no action needed.
Positive Highlights
- ✅
TestDefaultPlaywrightCLIVersionOutsideCooldownWindowkeeps the version honest; updating it alongside the constant is exactly the right pattern. - ✅ PR description is precise: includes the exact cooldown-expiry timestamp so CI reviewers know when the test will pass.
- ✅ Minimal, surgical change — only the two necessary lines touched in each file.
🧠 Reviewed using Matt Pocock's skills by Matt Pocock Skills Reviewer · 24 AIC · ⌖ 8.98 AIC · ⊞ 6.6K
Comment /matt to run again
There was a problem hiding this comment.
Patch bump looks correct. Version constant and test metadata (expectedVersion + publishedAtRFC3339) are consistently updated. No security or correctness concerns.
Note: The 72-hour npm cooldown for v0.1.15 expires at
2026-07-03T14:53:08Z— approximately 2 minutes after this review was run. The test will pass once CI executes past that threshold (as called out in the PR body).
🧵 Reviewed using Impeccable skills by Impeccable Skills Reviewer · 19.6 AIC · ⌖ 6.03 AIC · ⊞ 4.9K
🧪 Test Quality Sentinel Report✅ Test Quality Score: 100/100 — Excellent
📊 Metrics (1 test)
Verdict
Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "awmgmcpg"See Network Configuration for more information.
|
There was a problem hiding this comment.
Review: Routine Patch Bump
The only concern — the 72 h npm release-age cooldown expiring at 2026-07-03T14:53:08 UTC — is already captured by an existing review comment and is self-enforced by TestDefaultPlaywrightCLIVersionOutsideCooldownWindow; CI will hard-block if this merges too early. No code-correctness issues in the diff.
💡 Minor observation (non-blocking)
publishedAtRFC3339 is manually entered with no automated verification that it matches the actual npm publish time for 0.1.15. A wrong timestamp could silently shorten or lengthen the effective cooldown window. Consider cross-checking against the npm registry (npm view @playwright/cli@0.1.15 time.created) when automating future bumps.
🔎 Code quality review by PR Code Quality Reviewer · 38.4 AIC · ⌖ 5.46 AIC · ⊞ 5.4K
Comment /review to run again
|
@copilot please run the
|
Ran
Actions taken: No code changes needed — the only blocker was time (cooldown window). Local validation confirmed all checks pass. Hand-off: CI must be re-triggered by a maintainer (close/reopen PR, |
Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
PR Triage
Breakdown: Patch bump Batch: Can be reviewed alongside other dep/version bump PRs.
|
Patch version bump for
@playwright/cli. Updates the pinnedDefaultPlaywrightCLIVersionconstant and refreshes the cooldown-guard test metadata with the v0.1.15 npm publish timestamp.Changes
pkg/constants/version_constants.go—DefaultPlaywrightCLIVersion:"0.1.14"→"0.1.15"pkg/constants/version_constants_test.go— updateexpectedVersionandpublishedAtRFC3339(2026-06-30T14:53:08.941Z) inTestDefaultPlaywrightCLIVersionOutsideCooldownWindowThe 72-hour npm release-age cooldown for v0.1.15 expires at
2026-07-03T14:53:08Z; the test will pass once CI runs after that point.