Repository navigation
devops(release): prepare a patch release with a workflow - #3347
Merged
Pavel Feldman (pavelfeldman) merged 1 commit intoNov 13, 2026
Merged
Pavel Feldman (pavelfeldman) merged 1 commit into
Pavel Feldman (pavelfeldman) merged 1 commit into
Conversation
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Yury Semikhatsky (yury-s)
approved these changes
Nov 13, 2026
Pavel Feldman (pavelfeldman)
merged commit Nov 13, 2026
86a5f5a
into
microsoft:main
30 checks passed
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.
Agent: patch releaseworkflow. You start it by hand with a release branch, for examplerelease-1.65. It starts the Playwright bot on that branch.playwright-patch-releaseskill. It picks the next version after the last tag of the branch. The notes are the list of the fixes inmicrosoft/playwrightbetween the driver of the previous release and the driver of the tip of the branch, plus the browsers whose version changed.releasecall, in place of the draft of an earlier run. Only a maintainer publishes it.playwright-releaseskill now says that it is forv1.xx.0, with the full release notes.