-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Will HeroDevs maintain this project after August 2023? #524
Comments
If y'all do wind up seeing this issue, can you also please update the README for this project and Protractor as well? The README files for both repos currently say nothing about EOL status, so people are still participating in issues here. If nobody is going to answer issues then the repos should be configured to prevent new submissions. When NPM left Github (for a while), they put their repo in Archived status. |
@thw0rted Instructions to fix it yourself: #517 (comment) |
Thanks for the DIY method @alexsch01, and apologies on the delayed response. We're still exploring a few options on how we'll tackle issues like this, but what we can commit to is keeping protractor running in good form 🤘 @thw0rted thanks for pointing out the repo-level visibility concerns. I'll raise both points with our team & partners to get addressed asap |
@dwelch2344 Do you need some contribution helps for upgrade Protractor with latest selenium-webdriver (4.x) treatment? |
@StanislavKharchenko yes! We definitely care and are committed for the long haul of keeping Protractor running, which invariably means staying on top of browsers + tools + etc. Would love to chat. Shoot me an email and let's connect? Dave-at-HeroDevs.com |
Thank you, it works for me |
With Chromedriver 115 and above, Chromedriver downloads are moving to https://googlechromelabs.github.io/chrome-for-testing/
webdriver-manager update
will be stuck at Chromedriver 114When Chrome 116 is released to the Stable channel,
protractor
will no longer work@dwelch2344, will HeroDevs maintain this project?
The text was updated successfully, but these errors were encountered: