Feature and motivation
Right now users need to use GithubAPI to parse our released assets: https://github.com/SeleniumHQ/selenium/releases
We could publish an xml/json file (similar to https://chromedriver.storage.googleapis.com/) to make it easier for people to determine the location of a specific version of their desired asset.
We should be able to auto-generate this file using Github API via Github Actions.
Usage example
People can already use this if they need - https://api.github.com/repos/seleniumhq/selenium/releases
But it would be nice if it were more minimal and perhaps organized by Asset (e.g., Grid, IEDriver 32) rather than by version
Feature and motivation
Right now users need to use GithubAPI to parse our released assets: https://github.com/SeleniumHQ/selenium/releases
We could publish an xml/json file (similar to https://chromedriver.storage.googleapis.com/) to make it easier for people to determine the location of a specific version of their desired asset.
We should be able to auto-generate this file using Github API via Github Actions.
Usage example
People can already use this if they need - https://api.github.com/repos/seleniumhq/selenium/releases
But it would be nice if it were more minimal and perhaps organized by Asset (e.g., Grid, IEDriver 32) rather than by version