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

Pin selenium/standalone-chrome to 4.1.2-20220217. #514 #517

Merged
merged 1 commit into from Apr 7, 2022

Conversation

paul121
Copy link
Member

@paul121 paul121 commented Mar 31, 2022

No description provided.

@mstenta
Copy link
Member

mstenta commented Apr 7, 2022

Thanks @paul121! There is one other place where selenium/chrome-standalone:latest is referenced (in the documentation):

image: selenium/standalone-chrome:latest

If you don't mind, I'm going to amend your commit to change that as well. My thinking is: we don't know how long this pin will be in place, so might as well point devs in the right direction in our development docs too. And then, when #514 gets truly resolved, we can simply revert the commit from this PR to go back to latest in all three places. (Unless of course we decide against using latest, as you mentioned in #514 (comment).

@mstenta mstenta merged commit 5c764c5 into farmOS:2.x Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants