Actually I’m developing a tool that checks versions of a tool all along the chain (GitHub source code, Conda package and Galaxy Wrapper). Because we developed a bunch of tools and sometimes it’s hard to follow all the versions of multiple publishing platforms.
Then I use GitHub and Anaconda API through shields.io to get latest releases of tools with colored badges. As said in my first post, this is a little bit more tricky with the Galaxy ToolShed. We actually have a piece of code which get first the latest release ID and with that ID we are able to make a second request to get the latest version number. It’s a two-steps request which is not compliant with shields.io forged request. In addition, as the version number is inside nested dictionaries, I have to create a dummy JSON file to get it read by shields.io.
Maybe it should be useful to add the latest version of a ToolShed tool in the first-level of the response sent back from one single request.
Hi, @breakthewall and I, work in the same team.
We have noticed a spelling mistake in the webpage Galaxy Toolshed Api under the paragraph dedicated to the function get_repository_revision_install_info where the parameter changeset_revision is written as changset_revision
Another suggestion would be to add a version of the API in the url like: /api/repositories/get_repository_revision_install_info becomes /api/v1/repositories/get_repository_revision_install_info
Lastly, I’ve pushed a PR #7633 to the shields.io to make badges with the version of tools.