Skip to content

devops(release): prepare a patch release with a workflow - #3347

Merged
Pavel Feldman (pavelfeldman) merged 1 commit into
microsoft:mainfrom
pavelfeldman:agent-patch-release
Nov 13, 2026
Merged

Pavel Feldman (pavelfeldman) merged 1 commit into
microsoft:mainfrom
pavelfeldman:agent-patch-release

Conversation

@pavelfeldman

Copy link
Copy Markdown
Member
  • Add the Agent: patch release workflow. You start it by hand with a release branch, for example release-1.65. It starts the Playwright bot on that branch.
  • Add the playwright-patch-release skill. It picks the next version after the last tag of the branch. The notes are the list of the fixes in microsoft/playwright between the driver of the previous release and the driver of the tip of the branch, plus the browsers whose version changed.
  • The bot saves the notes as a draft release with its new release call, in place of the draft of an earlier run. Only a maintainer publishes it.
  • The playwright-release skill now says that it is for v1.xx.0, with the full release notes.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@pavelfeldman
Pavel Feldman (pavelfeldman) merged commit 86a5f5a into microsoft:main Nov 13, 2026
30 checks passed
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.

2 participants