Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
The chromedriver version increase we normally wouldn't backport in a patch release, but the axios update by itself is the key thing here. Does updating it require the major version update for Chromedriver?
chomedriver 86 depends on an old version of the lib, it's only v87 that depends on the correct version.
if add a dependency on the latest version of axios, chromedriver would still use the old version. So no way around updating the chromedriver version (and v87 has been out for 4 months already by now)
Comments
Comment #2
nod_Comment #3
nod_haha :þ
Comment #4
nod_Comment #5
catchLooks fine.
Comment #6
alexpottCommitted 63e9d5f and pushed to 9.2.x. Thanks!
Comment #8
xjmThe chromedriver version increase we normally wouldn't backport in a patch release, but the axios update by itself is the key thing here. Does updating it require the major version update for Chromedriver?
Comment #9
nod_chomedriver 86 depends on an old version of the lib, it's only v87 that depends on the correct version.
if add a dependency on the latest version of axios, chromedriver would still use the old version. So no way around updating the chromedriver version (and v87 has been out for 4 months already by now)
Comment #10
xjmOK great, thanks @nod_. In that case I'm going to backport it as-is to 9.1.x.
Comment #12
xjmI also confirmed that the problematic dependency wasn't present for 8.9.x (the older version of Chromedriver did not depend on it).