Commit Graph

2031 Commits

Author SHA1 Message Date
Andrey Lushnikov
2637805ace
feat(webkit): roll to 1208 (#1948) 2020-04-23 14:20:59 -07:00
Pavel Feldman
97a1aa554b docs: update version table 2020-04-23 13:50:12 -07:00
Pavel Feldman
40bed0f50c
docs: fix typos (#1947) 2020-04-23 13:40:34 -07:00
Ross Wollman
dc23c567c4
tests(downloads): add a test for Blob downloads (#1936) (#1939) 2020-04-23 13:02:37 -07:00
Pavel Feldman
471ccc72d3
browser(webkit): roll to ToT 4/23/2020 (#1943) 2020-04-23 12:20:37 -07:00
Pavel Feldman
2fcc2b5552
chore(chromium): resize browser frame when emulating viewport (#1924) 2020-04-23 10:38:58 -07:00
Pavel Feldman
fa59372248
browser(webkit): roll to ToT 4/22/2020 (#1940) 2020-04-23 10:34:31 -07:00
Arjun Attam
51ed5c5b4d
fix(examples): closes #1916 (#1934) 2020-04-23 08:44:58 -07:00
Max Schmitt
b516ac4fb2
fix: Dockerfile for Firefox (#1937) 2020-04-23 08:43:53 -07:00
Andrey Lushnikov
bf7430f75d docs(readme): remove FAQ link 2020-04-23 02:08:30 -07:00
Andrey Lushnikov
0b7f789de4
devops: try using another Github Actions event to trigger releases (#1931)
The [official
documentation](https://help.github.com/en/actions/language-and-framework-guides/publishing-nodejs-packages#publishing-packages-to-the-npm-registry)
suggests using `created` event, but it didn't work for us.

As someone mentioned on [github
community](https://github.community/t5/GitHub-Actions/Workflow-set-for-on-release-not-triggering-not-showing-up/m-p/53236#M8758),
it looks like the `created` event is actually issued when release draft
is first created.

Try using
[`published`](https://help.github.com/en/actions/reference/events-that-trigger-workflows#release-event-release)
event instead.
2020-04-22 22:52:32 -07:00
Dmitry Gozman
70d727d343
browser(webkit): ensure autorelease pools are drained on mac (#1933)
Drive-by: do not require 10.15-only QuickLookThumbnailing framework on 10.14.
2020-04-22 21:49:00 -07:00
Andrey Lushnikov
9bd55e9364
docs(readme.md): drop FAQ (#1930) 2020-04-22 18:05:59 -07:00
Andrey Lushnikov
e318ee5213 docs(readme): fix chromium version 2020-04-22 18:00:49 -07:00
Andrey Lushnikov
a147d3f99b
chore: sync versions across packages (#1929) 2020-04-22 17:43:13 -07:00
Andrey Lushnikov
511883d3f0
devops: fix checking if branch is tip-of-tree when publishing @next (#1926)
This should fix publishing @next from release branches.
2020-04-22 17:02:38 -07:00
Ross Wollman
53c78a8a29
fix(downloads): fix acceptDownloads complaint (#1777) (#1923) 2020-04-22 17:02:15 -07:00
Yury Semikhatsky
00e8d88777
fix: do not auto wait for downloads (#1921) 2020-04-22 15:08:39 -07:00
Pavel Feldman
fa6f738e4c
feat(browser): roll webkit to r1205 (#1922) 2020-04-22 14:50:56 -07:00
Yury Semikhatsky
b7afbf819f
fix(webkit): ignore WebSocket certificate errors on Mac (#1900) 2020-04-22 12:41:39 -07:00
Pavel Feldman
91c0631827
browser(webkit): extract webkit embedders into webkit/src (#1919) 2020-04-22 10:52:17 -07:00
Pavel Feldman
6ecac8c164
chore: restore networkidle0 alias (#1920) 2020-04-22 10:52:01 -07:00
Dmitry Gozman
95b8f61652
test: add more download tests (#1917) 2020-04-22 10:15:02 -07:00
Andrey Lushnikov
136173a93d
chore: cut v0.14.0 (#1913)
We will publish release from a branch.
2020-04-22 09:44:04 -07:00
Andrey Lushnikov
f8f3b8862c
docs(verification.md): fix typo 2020-04-22 00:32:46 -07:00
Andrey Lushnikov
2926d33a47
test: disable flaky firefox tests (#1912) 2020-04-22 00:07:02 -07:00
Andrey Lushnikov
89007c8f3d
devops: make README.md to always reflect tip-of-tree (#1911)
As of today, we have tooling in place that makes sure that our
main README.md **roughly** represents the state of the last release:
- browser versions and browser badges are those that we released last
- links to our API point to the last-released API version

This tooling, however, relies on the fact that every release is a sequence
of two consecutive commits:
- one commit that sets `package.json` version to a released version
- the following that "bumps" version to `-post`.

This release process is very unfortunate, because:
- it made releasing from branch impossible
- it required "freezing" commits to the master branch

This patch removes all the tooling and transitions `README.md` to always
represent tip-of-tree state. We will fully rely on
`https://playwright.dev` to show versioned docs.
2020-04-21 22:08:56 -07:00
Pavel Feldman
2313cebdca
browser(webkit): fix leaking popup windows (#1908) 2020-04-21 21:00:58 -07:00
Andrey Lushnikov
c474c540a3
devops: run CI against release branches too (#1910) 2020-04-21 19:20:19 -07:00
Joel Einbinder
48cbee1c32
browser(firefox): disable the extension blocklist (#1909)
This saves a few hundred milliseconds.
2020-04-21 17:59:27 -07:00
Andrey Lushnikov
0815ff36be
docs(browsers.md): fix nit 2020-04-21 17:19:10 -07:00
Pavel Feldman
fa18c419af
docs(browsers.md): updates and nits 2020-04-21 17:17:29 -07:00
Pavel Feldman
18650589e2
docs(browsers.md): updates and nits 2020-04-21 17:13:14 -07:00
Andrey Lushnikov
2d68830411
feat(testrunner): support --file to filter tests by test file name. (#1903) 2020-04-21 16:47:38 -07:00
Andrey Lushnikov
89b2fe5f38
feat: introduce PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD env variable (#1892) 2020-04-21 16:47:16 -07:00
Andrey Lushnikov
0935144c21
docs(browsers): add documentation describing managing browsers (#1907) 2020-04-21 16:38:40 -07:00
Arjun Attam
88366f3bb9
docs: adds introduction.md (#1905)
* docs: adds introduction.md

* elaborate on async/await pattern
2020-04-21 15:42:52 -07:00
Andrey Lushnikov
0f338eced7
devops: introduce release publishing workflow (#1894)
This workflow is based on the Github Actions docs: [publishing node.js
packages](https://help.github.com/en/actions/language-and-framework-guides/publishing-nodejs-packages)

It should be triggered once we create a github release.
It's unclear how to test this workflow, so I tried to re-use as much
code from `publish_canary.yml` as possible.
2020-04-21 15:10:00 -07:00
Yury Semikhatsky
e9914ccfea
docs: fix formatting 2020-04-21 11:28:08 -07:00
Yury Semikhatsky
18fb7f90ba
browser(webkit): ignore WebSocket HTTPS errors on Mac (#1899) 2020-04-21 10:38:28 -07:00
Pavel Feldman
74ce0412ad
browser(webkit): roll to ToT 4/20/2020 (#1898) 2020-04-21 09:45:49 -07:00
Andrey Lushnikov
96331de1f1
devops: start actually publishing @next versions for tip-of-tree commits (#1893)
The https://github.com/microsoft/playwright/runs/603719537 was pretty
successful.
2020-04-20 23:52:03 -07:00
Pavel Feldman
5b085fdf03
feat(logger): introduce context-level logger (#1896) 2020-04-20 23:24:53 -07:00
Pavel Feldman
2320d9cbf3
feat(webkit): roll to r1201 (#1897) 2020-04-20 22:25:44 -07:00
Dmitry Gozman
5d986317cf
test: add a test for non-navigation downloads (#1895) 2020-04-20 20:23:09 -07:00
Pavel Feldman
47c384112c
chore: bring back DEBUG= logging (#1891) 2020-04-20 20:00:55 -07:00
Andrey Lushnikov
068e1e00af devops: fix next version generation 2020-04-20 17:53:08 -07:00
Andrey Lushnikov
ac8a30c526
devops: start releasing from Github Actions (#1890)
This patch:
- removes releasing from Travis CI
- sets up a new GH Action that releases @next version from tip-of-tree

Once this GH Action proves to be working, we'll setup a `publish_release.yml`
workflow that will be triggered only by **release** github events
and that will publish released version with `LATEST` tag.

NOTE: this workflow does not actually run publishing - we're doing
`--dry-run` for now to see how it works in
`//utils/publish_all_packages.sh`.
2020-04-20 17:45:29 -07:00
Pavel Feldman
80a7fcd2de docs(verification): nits and typos 2020-04-20 17:35:50 -07:00
Dmitry Gozman
948d51d52c
fix(types): export selected types (#1881)
Currently exports LaunchOptions, BrowserContextOptions, Cookie and their deps.
2020-04-20 17:30:57 -07:00