What is the release page for the individual plugins?

[CarstenLeue]

The existence of https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases is awesome and helps with keeping our CI/CD pipelines up to date since we can automatically (via renovate) determine when a new build of the CLI is available and then update our toolchain.

How can we do the same for the plugins, e.g. the doi plugin?
Are there also release pages for the individual plugins so we know when to update? We'd like to avoid updating "live" when we run the CLI but rather do this in a controlled way.

[steveclay]

A simple way to do this might be to use the CLI plugin command. I'm assuming you just want to know about plug-ins that you are using. From a system that has the CLI and these plug-ins installed ibmcloud plugin list will show all the plug-ins, and indicate which need updated (have new versions). You can also ibmcloud plugin list --output json to get a more programmatically accessible list. For example it will have a Status entry like below for a plug-in that needs updated:

{
    "Name": "some-plugin",
    "Aliases": [ ],
    "Version": {
        "Major": 1,
        "Minor": 17,
        "Build": 0
    },
    "MinCliVersion": {
        "Major": 2,
        "Minor": 0,
        "Build": 0
    },
    "Namespaces": [],
    "Commands": [],
    "SDKVersion": {
        "Major": 1,
        "Minor": 7,
        "Build": 0
    },
    ...
    "Status": "Update Available"
}

[CarstenLeue]

I would actually like to integrate this into renovate, i.e. maintain an OCI image that has the latest plugins installed. And if there is a new version of a plugin I would like https://docs.renovatebot.com/ to update the version number, which would cause a new build of the OCI image with the updated plugin.
For this to work, renovate needs some way to tell if a new plugin version exists, e.g. by reaching out to git releases, an HTML file, a maven artifact,...

For the IBMCloudCLI we have these release pages. But for the plugins?

How does ibmcloud plugin list --output json find out if a new plugin exists, there must be some registry it consults.