Download the latest supported chromedriver for the version of Chrome installed by heroku-buildpack-google-chrome

[fkztw]

So, we can avoid the chromedriver version mismatch problem in a general situation.

The detail is in: heroku/heroku-buildpack-google-chrome#95

This PR should not be merged until the upstream repo PR been merged.

[fkztw]

I encountered a problem that there might be no same version of chromedriver for Google Chrome.

As the screenshot of build log below, https://chromedriver.storage.googleapis.com/85.0.4183.102/chromedriver_linux64.zip doesn't exist. (The latest version of chromedriver is only 85.0.4183.87 at this time.)

Close this PR at this time until I find a way to deal with this situation.

[pvande]

From the Chromedriver docs (http://chromedriver.chromium.org/downloads/version-selection):

Here are the steps to select the version of ChromeDriver to download:

• First, find out which version of Chrome you are using. Let's say you have Chrome 72.0.3626.81.
• Take the Chrome version number, remove the last part, and append the result to URL "https://chromedriver.storage.googleapis.com/LATEST_RELEASE_". For example, with Chrome version 72.0.3626.81, you'd get a URL "https://chromedriver.storage.googleapis.com/LATEST_RELEASE_72.0.3626".
• Use the URL created in the last step to retrieve a small file containing the version of ChromeDriver to use. For example, the above URL will get your a file containing "72.0.3626.69". (The actual number may change in the future, of course.)
• Use the version number retrieved from the previous step to construct the URL to download ChromeDriver. With version 72.0.3626.69, the URL would be "https://chromedriver.storage.googleapis.com/index.html?path=72.0.3626.69/".
• After the initial download, it is recommended that you occasionally go through the above process again to see if there are any bug fix releases.

[fkztw]

Works like a charm after using the new patch.
Thanks to @pvande.
Downloaded chromedriver 86.0.4240.22 for Google Chrome 86.0.4240.75.
And it works fine on my Heroku app.

How do I modify the CHANGELOG.md to pass the "Check changelog" GitHub Action? I know it only checks if there's diff for CHANGELOG.md. Is there any contribution guide about the format of the CHANGELOG.md? Or the maintainers will modify the CHANGELOG.md after reviewing the PR?

And just want to remind again. This PR is staled by heroku/heroku-buildpack-google-chrome#95. Should not be merged before that PR is merged.

[edmorley]

Hi! Sorry for the delay in replying to this PR. This buildpack isn't an officially supported buildpack so maintenance has been best-effort.

This buildpack has since been replaced by a new combined Chrome+chromedriver buildpack that resolves a number of issues:
https://github.com/heroku/heroku-buildpack-chrome-for-testing

As such this buildpack is being sunset.