docs: explain upgrading the Node-RED version via Stacks#7444
Merged
Conversation
Major Node-RED upgrades (e.g. Node-RED 5.0) are not delivered through an in-platform update button - they require creating a new Stack pinned to the new container, then moving Instances onto it. Add a generalised guide under docs/upgrade covering this, using the move to 5.0 as the worked example, and link it from the upgrade overview.
Drop the 'Good to know' and 'Questions?' footer sections (no other doc uses them) and simplify the intro/meta wording.
hardillb
reviewed
Jun 16, 2026
Co-authored-by: Ben Hardill <ben@flowforge.com>
hardillb
reviewed
Jun 16, 2026
hardillb
left a comment
hardillb
left a comment
Contributor
There was a problem hiding this comment.
Just a couple of additions to add a little more detail
Co-authored-by: Ben Hardill <ben@flowforge.com>
hardillb
approved these changes
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Self-hosted customers upgrading to a new major Node-RED version (e.g. Node-RED 5.0) are looking for an in-platform "update" button that doesn't exist — the Node-RED version is defined by an Instance's Stack, so the upgrade is done by creating a new Stack and moving Instances onto it.
This adds a generalised guide covering that process, using the move to 5.0 as the worked example, and links it from the upgrade overview.
Changes
docs/upgrade/nodered-version.md— Upgrading the Node-RED version. Explains why there's no update button, how to create the new Stack, and how to move new/existing Instances onto it. References the per-deployment Stacks docs and the existing Changing the Stack guide.docs/upgrade/README.md.Context
Came out of a support thread this morning (Nolte Küchen asking how to get to 5.0; related Maastricht upgrade ticket). Written to be general so it applies to any future major Node-RED version, not just 5.0.
Notes for reviewers
flowfuse/node-red:2.31.2-5.0.x— please sanity-check that tag.changestack.md) rather than the draft's "Change Node-RED Version".