It's been a few months since syncing changes from upstream, so more work than usual is needed to stabilize the trunk, so changes from upstream's trunk are being handled in this tmp branch and then will be merged into trunk once it's stable.
For #54 we can work on upgrading to Bookworm once we're stable.
Description
The way the Selenium version is updated has changed. It was changed in Base/Dockerfile and now is passed in as an environment variable, so I'm handling that in config.yml as well as the Makefile and build scripts.
Motivation and Context
Normally, syncing is quick and painless, but since some time went by, there's a bit more work involved to stabilize.
Types of changes
[X] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
It's been a few months since syncing changes from upstream, so more work than usual is needed to stabilize the trunk, so changes from upstream's trunk are being handled in this tmp branch and then will be merged into trunk once it's stable.
For #54 we can work on upgrading to Bookworm once we're stable.
Description
The way the Selenium version is updated has changed. It was changed in Base/Dockerfile and now is passed in as an environment variable, so I'm handling that in config.yml as well as the Makefile and build scripts.
Motivation and Context
Normally, syncing is quick and painless, but since some time went by, there's a bit more work involved to stabilize.
Types of changes
Checklist
Note that Chromium is still not building on newer Selenium versions past 4.10.0, so we may need to stay on Selenium 4.10.0 until https://github.com/seleniumhq-community/docker-seleniarm/issues/46 is resolved.