- docs
- FlowFuse User Manuals
- Using FlowFuse
-
- Getting Started
- Static asset service
- Bill of Materials
- FlowFuse Concepts
- Instance States
- Changing the Stack
- Custom Hostnames
- Custom Node Packages
- DevOps Pipelines
- Environment Variables
- FlowFuse Expert
- FlowFuse File Nodes
- FlowFuse MQTT Nodes
- FlowFuse Project Nodes
- FlowFuse Tables
- Groups
- High Availability mode
- HTTP Access Tokens
- Instance Settings
- Logging
- persistent-context
- Role-Based Access Control
- Shared Team Library
- Snapshots
- Team Broker
- Teams
- User Settings
- FlowFuse API
- Migrating a Node-RED project to FlowFuse
- Device Agent
- Device Agent
- Hardware Guides
- FlowFuse Cloud
- FlowFuse Cloud
- FlowFuse Self-Hosted
- Quick Start
- Installing FlowFuse
- Upgrading FlowFuse
- Administering FlowFuse
- Support
- Community Support
- Premium Support
- Debugging Node-RED issues
- Contributing
- Contributing to FlowFuse
Upgrading the Node-RED version
A new major version of Node-RED - such as Node-RED 5.0 - does not arrive through an in-editor or in-platform "update" button. The version of Node-RED an Instance runs is defined by its Stack. To move to a new major version you add it as a new Stack, then point your Instances at it.
This page uses the move to Node-RED 5.0 as an example, but the same steps apply to any major Node-RED version upgrade.
Why there's no update button
The notification and one-click upgrade you may have seen applies to new versions of an existing Stack (see Managing Stacks). Crossing a major Node-RED version is different: you create a new Stack that pins the new container, rather than upgrading the existing Stack in place. This keeps the two versions side by side so you can move Instances over at your own pace. It also ensures major version upgrades are not automatically applied by the Scheduled Maintenance feature.
Before you start
- You will need access to Admin Settings.
- Add the new Node-RED version as a distinct new Stack rather than editing your existing Stack. Keeping them separate means your current Instances stay on their existing version until you choose to move them, and you can switch back from an Instance's settings if needed.
Create the new Stack
- Go to Admin Settings → Stacks.
- Click Create Stack.
- Set the Container Location to the image for the new Node-RED version. The exact value depends on your deployment model - see the deployment-specific guides below. For Node-RED 5.0 on Docker or Kubernetes this is
flowfuse/node-red:2.31.2-5.0.x; the full list of pre-built tags is on Docker Hub. (tags are of the form [FlowFuse Version]-[Node-RED Version]) - Save the Stack. It is now available when you create or migrate Instances.
For the details of how the Container Location is specified for each deployment model, see:
Use the new Stack
For a new Instance
Select the new Stack when you create the Instance. It starts on the new Node-RED version right away.
For an existing Instance
Move the Instance onto the new Stack by following Changing the Stack: open the Instance's Settings tab and use Change Instance Stack to select the new Stack. The Instance restarts on the new Stack.
