puppeteer

thunderstrike/puppeteer

Fork 0

Commit Graph

Author	SHA1	Message	Date
Andrey Lushnikov	b7e922b5f5	chore: fix puppeteer@next race condition (#3209 ) When we merge commits to master, Travis kicks job to build a new commit and to publish new version of puppeteer@next. If two commits are landed in almost the same time, then travis starts two parallel jobs to build each commit. This race condition results in the incorrect puppeteer@next revision. This patch teaches apply_next_version.js to verify if current HEAD is matching upstream HEAD. If it doesn't, the predeploy hook fails which (hopefully) aborts deployment. Fixes #2925.	2018-09-06 20:57:35 +01:00
JoelEinbinder	bd73e4b7b8	chore: use unique version for puppeteer@next (#1688 ) This patch starts amending package.json with a unique puppeteer@next version so that it gets published on npm.	2017-12-28 17:19:13 -08:00

Author

SHA1

Message

Date

Andrey Lushnikov

b7e922b5f5

chore: fix puppeteer@next race condition (#3209 )

When we merge commits to master, Travis kicks job to build a new commit
and to publish new version of puppeteer@next.

If two commits are landed in almost the same time, then travis starts
two parallel jobs to build each commit. This race condition results
in the incorrect puppeteer@next revision.

This patch teaches apply_next_version.js to verify if current HEAD
is matching upstream HEAD. If it doesn't, the predeploy hook fails
which (hopefully) aborts deployment.

Fixes #2925.

2018-09-06 20:57:35 +01:00

JoelEinbinder

bd73e4b7b8

chore: use unique version for puppeteer@next (#1688 )

This patch starts amending package.json with a unique puppeteer@next version
so that it gets published on npm.

2017-12-28 17:19:13 -08:00

2 Commits