Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Proposed changes

So that an integrators can determine if updates are available:

• Allow access to available updates via RED API RED.palette.editor.getAvailableUpdates()
  • This permits integrator to request state of updates (init time)
• Emit event "registry:updates-available" to emit updates on changes
  • This permits reactive integration (without polling

Example usage

        let nrUpdates
        function init () {
            // get state on startup
            nrUpdates = RED.palette.editor.getAvailableUpdates()
        }
        
        // receive updates reactively as they occur
        RED.events.on("registry:updates-available", (updates) => {
            nrUpdates = updates
            console.log("Updates available", updates)
        })

Example Output 1 palette item update available

{
    "count": 1,
    "core": null,
    "palette": [
        {
            "package": "node-red-contrib-thing",
            "current": "0.10.2-dev",
            "latest": "0.10.3"
        }
    ]
}

Example Output 1 palette item and core update available

{
    "count": 2,
    "core": {
            "current": "4.1.6",
            "latest": "5.0.0"        
    },
    "palette": [
        {
            "package": "node-red-contrib-thing",
            "current": "0.10.2-dev",
            "latest": "0.10.3"
        }
    ]
}

Example Output available updates cleared due to user updating

{
    "count": 0,
    "core": null,
    "palette": []
}

Checklist

• I have read the contribution guidelines
• For non-bugfix PRs, I have discussed this change on the forum/slack team.
• I have run npm run test to verify the unit tests pass
• I have added suitable unit tests to cover the new/changed functionality