Skip to content

Commit

Permalink
docs: update release instructions (#30)
Browse files Browse the repository at this point in the history
  • Loading branch information
yury-s committed Aug 3, 2020
1 parent 24e3614 commit 13542e6
Showing 1 changed file with 11 additions and 3 deletions.
14 changes: 11 additions & 3 deletions DEVELOPMENT.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,14 +12,22 @@ npm run package

## Releases

1. Draft a new release on GitHub.
1. Create a semver tag pointing to the commit you want to release. E.g. to create `v1.4.4` from tip-of-tree:
```
git checkout master
git pull upstream master
git tag v1.4.4
git push upstream v1.4.4
```
1. Create Playwrgight PR with updated reference to the GitHub action (change `playwright-github-action@v1` to the newly created version `playwright-github-action@v1.4.4`) and make sure the tests are passing. Do not commit the change.
1. Draft a new release on GitHub using the semver tag.
1. Update the sliding tag (`v1`) to point to the new release commit. Note that existing users relying on the `v1` will get auto-updated.

### Updating sliding tag

Follow these steps to move the `v1` to a new commit `1e2d565`.
Follow these steps to move the `v1` to a new version `v1.4.4`.

```
git tag -f v1 1e2d565
git tag -f v1 v1.4.4
git push -f upstream v1
```

0 comments on commit 13542e6

Please sign in to comment.