Skip to content

Verify selenium 4.12.0, and then ship a new seleniumbase release with it #2047

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.

Sign up for GitHub

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

Jump to bottom
Closed
mdmintz opened this issue Sep 1, 2023 · 2 comments · Fixed by #2053
Closed

Verify selenium 4.12.0, and then ship a new seleniumbase release with it #2047

mdmintz opened this issue Sep 1, 2023 · 2 comments · Fixed by #2053
Assignees
@mdmintz
Labels
dependencies This involves updating a dependency file SeleniumBase 4 SeleniumBase 4

Comments

@mdmintz
Copy link
Member

mdmintz commented Sep 1, 2023

Verify selenium 4.12.0, and then ship a new seleniumbase release with it

There were several changes, so everything should be checked carefully before upgrading dependencies.

Also include: #1979
@mdmintz mdmintz added dependencies This involves updating a dependency file SeleniumBase 4 SeleniumBase 4 labels Sep 1, 2023
@mdmintz mdmintz self-assigned this Sep 1, 2023
@mdmintz mdmintz mentioned this issue Sep 1, 2023
Merged
@mdmintz
Copy link
Member Author

mdmintz commented Sep 1, 2023

This was resolved in 4.18.0 - https://github.com/seleniumbase/SeleniumBase/releases/tag/v4.18.0

@mdmintz
Copy link
Member Author

mdmintz commented Sep 8, 2023

Note that a rollback occurred shortly after this release. Details: #2056

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mdmintz mdmintz

Labels
dependencies This involves updating a dependency file SeleniumBase 4 SeleniumBase 4
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Upgrade Selenium to 4.12.0 seleniumbase/SeleniumBase
1 participant
@mdmintz