Update version pinned dependencies

[ttys0dev]

Lets update these to their latest versions.

[mlissner]

Did you read these release notes?

[ttys0dev]

Looked to be bug fixes from what I could tell.

[ttys0dev]

@mlissner does this look good to merge?

[mlissner]

Hm, I'm fine upgrading most of these, but selenium tends to have a lot of broken pieces. We can give it a shot, but I suspect it'll break things.

[ttys0dev]

We can give it a shot, but I suspect it'll break things.

I guess we need a new release here as well? Or are there some additional tests that we should run before hand?

[ttys0dev]

Tests in courtlistener pass with updated selenium as well, just needed to make this tweak.

[mlissner]

I think it should be fine. I think we use Selenium in three ways:

• tests, here
• tests in CL
• to scrape, using a headless scraper defined in k8s as a pod (or perhaps a deployment)

So monkeying with it here should affect anything and I don't think it even needs a release.

[ttys0dev]

I don't think it even needs a release.

Well if we don't have a release we have to use a git dependency in courtlistener like {git = "https://github.com/freelawproject/juriscraper.git", branch="main"} in order to use the newer selenium version.

[mlissner]

I don't think so. CL sets a variable that means it uses a remote selenium driver instead of the one that's part of Juriscraper. Check out WEBDRIVER_CONN.

[ttys0dev]

Check out WEBDRIVER_CONN.

Oh, that's for using a remote webdriver server I think, I'm just referring to updating the python client library version.

[mlissner]

Hm, right, OK. @albertisfu could you do a release of Juriscraper when you get a sec, please?

[albertisfu]

Sure, Juriscraper 2.4.8 release is ready.