Skip to content
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.

Use webdriver-manager-replacement #5087

Closed
cnishina opened this issue Dec 11, 2018 · 1 comment
Closed

Use webdriver-manager-replacement #5087

cnishina opened this issue Dec 11, 2018 · 1 comment

Comments

@cnishina
Copy link
Member

Until I can publish to Angular, we will remove webdriver-manager for webdriver-manager-replacement. When I have publishing permissions, I'll remove the webdriver-manager-replacement for the beta release.

@cnishina cnishina added this to the selenium4 upgrade milestone Dec 11, 2018
@cnishina cnishina self-assigned this Dec 11, 2018
cnishina added a commit to cnishina/protractor that referenced this issue Dec 12, 2018
- Current workaround to use webdriver-manager-replacement until we
publish a beta release of webdriver-manager

closes angular#5087
cnishina added a commit that referenced this issue Dec 12, 2018
- Current workaround to use webdriver-manager-replacement until we
publish a beta release of webdriver-manager

closes #5087
@cnishina
Copy link
Member Author

Closed with #5088

cnishina added a commit to cnishina/protractor that referenced this issue Dec 19, 2018
- Current workaround to use webdriver-manager-replacement until we
publish a beta release of webdriver-manager

closes angular#5087
cnishina added a commit to cnishina/protractor that referenced this issue Mar 23, 2019
- Current workaround to use webdriver-manager-replacement until we
publish a beta release of webdriver-manager

closes angular#5087
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant