microsoft/playwright
1
1
Fork 0
mirror of https://github.com/microsoft/playwright.git synced 2024-12-14 21:53:35 +03:00
Code Issues Projects Releases Wiki Activity
083b54a64e
playwright/.github/workflows/publish_canary_npm.yml

34 lines
959 B
YAML
Raw Normal View History

chore: fix devrelease workflow names (#3717)
2020-09-02 02:51:32 +03:00
name: "devrelease:npm"
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-21 03:45:29 +03:00
on:
devops: introduce manual @next NPM publishing (#6881)
2021-06-04 00:50:40 +03:00
workflow_dispatch:
devops: start publishing canary at midnight every day (#5343) This patch: - starts publishing canary NPM package at 00:10AM UTC - canary version is published from default (`master`) branch and is named with a date. E.g. for a version published on Feb 5, 2021, the version would be `1.8.0-alpha-feb-5-2021` - versions from release branches are still published on every commit and have the regular commit timestamp suffix
2021-02-10 01:28:04 +03:00
schedule:
- cron: "10 0 * * *"
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-21 03:45:29 +03:00
push:
branches:
devops: run CI against release branches too (#1910)
2020-04-22 05:20:19 +03:00
- release-*
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-21 03:45:29 +03:00
jobs:
devops: fix docker publishing (#2939) - Repository name has to start with `public/` to be exported to dockerhub. - Remove `DOCKER_USERNAME` to avoid unnecessary masking in our logs. - Publish dev versions of Docker image only when changes to docker file happen. (this is why NPM publishing and Docker publishing for dev releases are now separate). - Release publishing in two separate jobs to make them independent. References #2926
2020-07-14 03:15:10 +03:00
publish-canary-npm:
name: "publish to NPM"
devops: use ubuntu focal on bots and docs (#5951) - drive-by: updated NPM Action - replaced ubuntu-latest by ubuntu-20 so its pinned Extracted from #5746
2021-04-05 22:39:15 +03:00
runs-on: ubuntu-20.04
devops: avoid running publish on external contrib (#3257) Everytime I sync my fork to upstream, I get failure notifications: ``` Run failed for master (3edfb2a) Repository: rwoll/playwright Workflow: devrelease Duration: 10 minutes and 34.0 seconds Finished: 2020-07-31 18:30:13 UTC ``` Since forks should never have the necessary secrets to publish the npm and Docker packages, we limit the running of these jobs to avoid noisy failures for contributors.
2020-08-01 00:09:36 +03:00
if: github.repository == 'microsoft/playwright'
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-21 03:45:29 +03:00
steps:
- uses: actions/checkout@v2
devops: use ubuntu focal on bots and docs (#5951) - drive-by: updated NPM Action - replaced ubuntu-latest by ubuntu-20 so its pinned Extracted from #5746
2021-04-05 22:39:15 +03:00
- uses: actions/setup-node@v2
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-21 03:45:29 +03:00
with:
chore: drop support for Node.js 10 (#6371)
2021-04-30 17:49:10 +03:00
node-version: 12
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-21 03:45:29 +03:00
registry-url: 'https://registry.npmjs.org'
chore: migrate to monorepo (#9421)
2021-10-11 17:52:17 +03:00
- run: npm i -g npm@7
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-21 03:45:29 +03:00
- run: npm ci
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-02 01:22:29 +03:00
- run: npm run build
chore: migrate to monorepo (#9421)
2021-10-11 17:52:17 +03:00
- run: npx playwright install-deps
devops: start publishing canary at midnight every day (#5343) This patch: - starts publishing canary NPM package at 00:10AM UTC - canary version is published from default (`master`) branch and is named with a date. E.g. for a version published on Feb 5, 2021, the version would be `1.8.0-alpha-feb-5-2021` - versions from release branches are still published on every commit and have the regular commit timestamp suffix
2021-02-10 01:28:04 +03:00
- run: node utils/build/update_canary_version.js --today-date
devops: introduce manual @next NPM publishing (#6881)
2021-06-04 00:50:40 +03:00
if: contains(github.ref, 'master') && github.event_name != 'workflow_dispatch'
devops: start publishing canary at midnight every day (#5343) This patch: - starts publishing canary NPM package at 00:10AM UTC - canary version is published from default (`master`) branch and is named with a date. E.g. for a version published on Feb 5, 2021, the version would be `1.8.0-alpha-feb-5-2021` - versions from release branches are still published on every commit and have the regular commit timestamp suffix
2021-02-10 01:28:04 +03:00
- run: node utils/build/update_canary_version.js --commit-timestamp
devops: introduce manual @next NPM publishing (#6881)
2021-06-04 00:50:40 +03:00
if: contains(github.ref, 'release') || github.event_name == 'workflow_dispatch'
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-21 03:45:29 +03:00
- run: utils/publish_all_packages.sh --tip-of-tree
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
Reference in New Issue Copy Permalink