Extracted gecko and chrome drivers have version number in filename. It shouldn't.

[AllanMedeiros]

Both gecko and chrome driver are downloaded as zip files with version numbers in file names.
Each zip has the driver without the version number, but webdriver-manager is adding the version number to the .exe file name on extracting them.
This makes harder to keep driver path updated, as we have to update the path everytime to point to the new file.
Also many tools by default try to run chromedriver.exe and not something like chromedriver_76.0.X.exe.

[cnishina]

Could be worth looking into again. However, this is as designed and was done to keep track of different binaries previously downloaded. What other tools are running ChromeDriver? Could you just read the file path off of the update-config.json file?

[cnishina]

I think this is okay to remove the version numbers. We were keeping track of these because there was a world when we might want to have two different versions of ChromeDriver. We can remove the version of this until someone complains.

This will be done against the master branch and will eventually be in 13...whenever that is released.

[AllanMedeiros]

If someone needs to keep a history of downloaded binaries, then the zip files could be left there after newer drivers are downloaded, but from my view is not necessary as it is easy to get a specific driver version from the command line anyway.

[YevheniiaMazur]

Is there any workaround for this issue? For now, it blocks usage of webdriver-manager with selenium tests for me