What problem does it solve?
Releasing a new Playwright Java version involves many error-prone manual steps: cutting the release branch, bumping Maven versions across 11 pom files, translating JS-flavored release notes into Java API names, and ticking internal checklist items. This Skill codifies that entire post-roll release procedure.
Core Features & Use Cases
- Release branch management: Pushes
release-1.X from upstream main after the driver roll PR merges.
- Maven version marking: Runs
set_maven_version.sh and validates the expected 11-pom diff, flagging unexpected changes.
- GitHub release drafting: Generates release notes via the upstream renderer, applies Java-specific API name substitutions (e.g.
toMatchAriaSnapshot() → matchesAriaSnapshot()), and creates a draft release targeting the release branch.
- Checklist tracking: Incrementally ticks Java items in the internal
microsoft/playwright-internal release checklist issue via the GitHub API.
- Use Case: After the
chore: roll driver to 1.60.0 PR merges, invoke this Skill to cut release-1.60, mark version 1.60.0, and draft the v1.60.0 GitHub release.
Quick Start
Prepare the Playwright Java v1.X.0 release now that the driver roll PR has merged, including the release branch, Maven version bump, and draft GitHub release.