playwright/utils/apply_next_version.js

const {execSync} = require('child_process');

const package = require('../package.json');
let version = package.version;
const dashIndex = version.indexOf('-');
if (dashIndex !== -1)
  version = version.substring(0, dashIndex);
version += '-next.' + Date.now();
console.log('Setting version to ' + version);

execSync(`npm --no-git-tag-version version ${version}`);
chore: fix utils/apply_next_version.js 2020-03-03 05:17:16 +03:00			`const {execSync} = require('child_process');`

Initial commit 2019-11-19 05:18:28 +03:00			`const package = require('../package.json');`
			`let version = package.version;`
			`const dashIndex = version.indexOf('-');`
			`if (dashIndex !== -1)`
			`version = version.substring(0, dashIndex);`
chore(ci): another attempt to program in .travis.yml 2020-02-29 03:17:59 +03:00			`version += '-next.' + Date.now();`
Initial commit 2019-11-19 05:18:28 +03:00			`console.log('Setting version to ' + version);`
feat: setup continuous deployment (#1159) This patch sets continuous deployment of playwright packages from tip-of-tree. These packages are released under the "@next", so it should be possible to install tip-of-tree version of Playwright from NPM using ``` npm i playwright@next ``` A few technical details: - This uses travis to drive deployments - This deploys from master and only if all browsers pass all tests on linux - This is an attempt to deploy just two packages: `playwright-core` and `playwright-firefox`. If this works out, I'll follow-up with other packages as well 2020-02-28 22:02:42 +03:00
			execSync(`npm --no-git-tag-version version ${version}`);