playwright/docs/development/releasing.md

Preparing release notes

1. Use "draft new release tag".
2. Version starts with "v", e.g. "v1.1.0".
3. Fill "Raw notes".
   • git fetch --tags upstream
   • git log --pretty="%h - %s" v1.0.0..HEAD
4. Fill "Bug fixes".
   • git log v0.11.1..HEAD
   • Manually look for #1234 references in commit messages.
5. Fill "Current status".
   • node utils/print_versions.js
   • Copy tests status from IsPlaywrightReady.
6. Fill "Highlights" if any.
   • Be creative.
7. Fill "Breaking API Changes" if any.
   • git diff v0.11.1:docs/api.md docs/api.md
8. Fill "New APIs" if any.
   • git diff v0.11.1:docs/api.md docs/api.md
9. When making links to the API, copy actual links from GitHub, and not from api.md source - these might be incorrect.
   • Before publishing, replace blob/master/docs with blob/v1.1.0/docs in all the links.
10. Use "Save Draft", not "Publish".

Releasing to npm

1. Mark a new version.
   • Bump package.json version to vXXX.YYY.ZZZ.
   • npm run doc to update documentation links.
   • Send a PR titled chore: mark version vXXX.YYY.ZZZ.
   • Make sure the PR passes all required checks.
   • Merge it.
2. Click 'Publish release' button on the prepared release notes.
3. Publish to npm.
   • npm login
   • node utils/publish_all_packages.sh --release
4. Mark post release.
   • Bump package.json version to vXXX.YYY.ZZZ-post.
   • npm run doc to update documentation links.
   • Merge a PR titled chore: bump version to vXXX.YYY.ZZZ-post.
   • NOTE: no other commits should be landed in-between release commit and bump commit.