3 commits

Author	SHA1	Message	Date
Dmitry Gozman	5c4751d5dd	chore: generate protocol during browser roll (#2719) ... We now commit protocol.ts files during the roll. New utils/roll_browser.js helps with that. This makes our installation very shallow: - build installer; - download browsers.	2020-07-01 15:22:29 -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
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