Skip to content
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

Open
alexsch01 opened this issue Jul 21, 2023 · 6 comments
Open

Will HeroDevs maintain this project after August 2023? #524

alexsch01 opened this issue Jul 21, 2023 · 6 comments

Comments

@alexsch01
Copy link

alexsch01 commented Jul 21, 2023

With Chromedriver 115 and above, Chromedriver downloads are moving to https://googlechromelabs.github.io/chrome-for-testing/

  • this means webdriver-manager update will be stuck at Chromedriver 114

When Chrome 116 is released to the Stable channel, protractor will no longer work

@dwelch2344, will HeroDevs maintain this project?

@thw0rted
Copy link

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.

@alexsch01
Copy link
Author

@thw0rted Instructions to fix it yourself: #517 (comment)

@dwelch2344
Copy link

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

@StanislavKharchenko
Copy link

@dwelch2344 Do you need some contribution helps for upgrade Protractor with latest selenium-webdriver (4.x) treatment?
This approach will eliminate needs to use webdriver-manager, but just rely on selenium-manager which now works and maintain driver updates under the hood.
There are also more things from selenium 4, which is fully w3c and has broader browser supports. Selenium 3 is deprecated (JWP deprecated as well) and some time it will stop working with modern browsers (Protractor 7 will also stop working)

@dwelch2344
Copy link

@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

@VolodymyrDmytriukhin
Copy link

@thw0rted Instructions to fix it yourself: #517 (comment)

Thank you, it works for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants