Update protractor to the latest version 🚀#106
Conversation
Version 5.2.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 15 commits.
See the full diff |
Version 5.2.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 3 commits.
See the full diff |
Version 5.3.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 12 commits.
See the full diff |
Version 5.3.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 8 commits.
See the full diff |
Version 5.4.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 15 commits ahead by 15, behind by 1.
See the full diff |
Version 5.4.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 8 commits ahead by 8, behind by 1.
See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 7 commits ahead by 7, behind by 1.
See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 63 commits.
There are 63 commits in total. See the full diff |
|
🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚 Find out how to migrate to Snyk at greenkeeper.io
Update to this version instead 🚀 CommitsThe new version differs by 17 commits ahead by 17, behind by 63.
There are 17 commits in total. See the full diff |
Version 5.2.0 of protractor was just published.
The version 5.2.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of protractor.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 20 commits.
c2cf0dbchore(release): version changelog for 5.2.00fbc2c0chore(release): update selenium-webdriverjs and bump version number (#4538)862e8befix(circleci): Disable testcases for "useBlockingProxy" (#4523)f7e17f3fix(clientSideScripts): change protractor to support waiting for hybrid app (#4512)15776b8Export Locator (#4459)6be98eadocs(plugins): fix links and formatting (#4431)4b7cadafix(sauce): bring back sauceProxy as a configuration option (#4419)b87159bfix(website): fix all locator examples to useelementoverbrowser.findElement(#4413)768fd39fix(local): allow local driver provider to use gecko driver from config (#4412)c0b8770docs(website): fix issue 4246f79938edocs(plugins): add ng-apimock plugin to plugins.mdab1afb0fix(blockingproxy): Start bpRunner strictly after setupDriverEnvb85e7eefix(npmignore): .map files in built directory cause stacktrace lines to nowhere299fc8ddocs(browser-support): Fixed incorrect examplee5a5d59docs(frameworks) align cucumberOpts commentsThere are 20 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴