Upgrading Bee
It's very important to keep Bee up to date to benefit from security updates and ensure you are able to properly interact with the Swarm network. The #node-operators channel is an excellent resource for any of your questions regarding node operation.
Bee sure to back up your keys and cash out your cheques to ensure your xBZZ is safe before applying updates.
Nodes should not be shut down or updated in the middle of a round they are playing in as it may cause them to lose out on winnings or become frozen. To see if your node is playing the current round, check if lastPlayedRound equals round in the output from the /redistributionstate endpoint. See staking section for more information on staking and troubleshooting.
Version compatibility and upgrade path
The Swarm network has a minimum supported Bee version. The minimum supported version is currently v2.8.0, the release that introduced a breaking p2p protocol change, so nodes running an older protocol can no longer connect to the network.
When upgrading across a breaking protocol change, do not skip the release that introduced it. Upgrade through that version so any one-time data migrations run while they still exist in the code, since Bee removes old migration and compatibility code once a version is no longer supported.
Bee v2.8.2 is non-disruptive for nodes already on v2.8.0 or v2.8.1: it makes no breaking p2p protocol changes, so you can upgrade in place using the steps below.
If you are running Bee v2.6.0 or older: Bee v2.8.1 removed the last of the v2.6.0 backward-compatibility code, so you cannot upgrade directly to v2.8.1 or later. Either upgrade stepwise (v2.6.0 → v2.8.0 → v2.8.2) so the data migrations run, or reinstall the node fresh on v2.8.2.
If you have tracing enabled, note that Bee v2.8.2 replaces Jaeger/OpenTracing with OpenTelemetry (OTLP export).
Point tracing-endpoint at an OTLP-capable collector before upgrading, and review the new tracing options in the v2.8.2 release notes.
With tracing disabled, nothing changes.
Ubuntu / Debian
To upgrade Bee, first stop the Bee service:
sudo systemctl stop bee
Next, upgrade the bee package:
sudo apt-get update
sudo apt-get upgrade bee
You will see output like this after a successful upgrade:
The following packages will be upgraded:
bee
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 57.1 MB of archives.
After this operation, 3120 kB of additional disk space will be used.
Preparing to unpack .../archives/bee_2.8.2_arm64.deb ...
Unpacking bee (2.8.2) over (2.8.1) ...
Setting up bee (2.8.2) ...
Installing new version of config file /etc/bee/bee.yaml ...
If you have edited /etc/bee/bee.yaml, the upgrade stops and asks what to do with it:
Configuration file '/etc/bee/bee.yaml'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** bee.yaml (Y/I/N/O/D/Z) [default=N] ?
Answer N to keep your configuration, including your password and RPC endpoint.
The new default configuration is saved next to it as /etc/bee/bee.yaml.dpkg-dist, so you can compare the two afterwards.
Answering Y replaces your configuration with the default one.
You may now start your node again:
sudo systemctl start bee
Manual Installations
To upgrade your manual installation, simply stop Bee, replace the Bee binary and restart.
If you installed Bee with the shell script, you can replace the binary by running the script again with the new version's TAG.
Docker
To upgrade your Docker installation, simply increment the version number in your configuration and restart.