yjkellyjoo · Oct 15, 2026 · Sep 10, 2026 · Oct 7, 2026 · Oct 7, 2026
diff --git a/docs/bee/installation/build-from-source.md b/docs/bee/installation/build-from-source.md
@@ -32,7 +32,7 @@ Prerequisites for installing directly from source are:
 3. Checkout the required version:
 
    ```bash
-   git checkout v2.8.1
+   git checkout v2.8.2
    ```
 
 4. Build the binary:
@@ -48,7 +48,7 @@ Prerequisites for installing directly from source are:
    ```
 
    ```
-   2.8.1
+   2.8.2
    ```
 
 6. (optional) Additionally, you may also like to move the Bee binary to somewhere in your `$PATH`

diff --git a/docs/bee/installation/docker.md b/docs/bee/installation/docker.md
@@ -7,9 +7,9 @@ description: Provides comprehensive steps for deploying Bee nodes using Docker c
 The following is a guide for installing a Bee node using Docker. Docker images for Bee are hosted at [Docker Hub](https://hub.docker.com/r/ethersphere/bee). Using Docker to operate your Bee node offers many benefits, such as ease of deployment and consistency across environments. 
 
 :::caution
-In the examples below we specify the exact image version as 2.8.1. 
+In the examples below we specify the exact image version as 2.8.2. 
 It's recommended to only use the exact version number tags. 
-Make sure to check that you're on the latest version of Bee by reviewing the tags for Bee on [Docker Hub](https://hub.docker.com/r/ethersphere/bee/tags), and replace 2.8.1 in the commands below if there is a newer full release. 
+Make sure to check that you're on the latest version of Bee by reviewing the tags for Bee on [Docker Hub](https://hub.docker.com/r/ethersphere/bee/tags), and replace 2.8.2 in the commands below if there is a newer full release. 
 :::
 
 :::warning
@@ -39,13 +39,13 @@ docker run -d --name bee-1 \
   -e BEE_PASSWORD="flummoxedgranitecarrot" \
   -e BEE_BLOCKCHAIN_RPC_ENDPOINT="https://xdai.fairdatasociety.org" \
   -v bee-1:/home/bee/.bee \
-  ethersphere/bee:2.8.1 start
+  ethersphere/bee:2.8.2 start
 ```
 
 Here is the same command in a single line in case you run into issues with the line breaks in the command above:
 
 ```bash
-docker run -d --name bee-1 --restart always -p 127.0.0.1:1633:1633 -p 1634:1634 -e BEE_API_ADDR=":1633" -e BEE_FULL_NODE="true" -e BEE_SWAP_ENABLE="true" -e BEE_PASSWORD="flummoxedgranitecarrot" -e BEE_BLOCKCHAIN_RPC_ENDPOINT="https://xdai.fairdatasociety.org" -v bee-1:/home/bee/.bee ethersphere/bee:2.8.1 start
+docker run -d --name bee-1 --restart always -p 127.0.0.1:1633:1633 -p 1634:1634 -e BEE_API_ADDR=":1633" -e BEE_FULL_NODE="true" -e BEE_SWAP_ENABLE="true" -e BEE_PASSWORD="flummoxedgranitecarrot" -e BEE_BLOCKCHAIN_RPC_ENDPOINT="https://xdai.fairdatasociety.org" -v bee-1:/home/bee/.bee ethersphere/bee:2.8.2 start
 ```
 
 #### Command explained:
@@ -61,7 +61,7 @@ docker run -d --name bee-1 --restart always -p 127.0.0.1:1633:1633 -p 1634:1634
 - **`-e BEE_PASSWORD="flummoxedgranitecarrot"`**: Sets the keystore password, make sure to replace with your own.
 - **`-e BEE_BLOCKCHAIN_RPC_ENDPOINT="https://xdai.fairdatasociety.org"`**: Connects to the Gnosis Chain.
 - **`-v bee-1:/home/bee/.bee`**: Persists node data in the `bee-1` volume.
-- **`ethersphere/bee:2.8.1 start`**: Runs Bee version 2.8.1 and starts the node.
+- **`ethersphere/bee:2.8.2 start`**: Runs Bee version 2.8.2 and starts the node.
 
 This setup runs the Bee node in a container, with full node functionality, SWAP enabled, and connections to the Gnosis blockchain for chequebook and postage stamp management, while persisting its data using a volume. 
 
@@ -77,7 +77,7 @@ If everything is set up correctly, you should see your Bee node listed:
 
 ```bash
 CONTAINER ID     IMAGE     COMMAND     CREATED     STATUS     PORTS     NAMES
-37f4ad8b4060   ethersphere/bee:2.8.1   "bee start"   6 seconds ago   Up 5 seconds   127.0.0.1:1633->1633/tcp, 0.0.0.0:1634->1634/tcp, :::1634->1634/tcp   bee-1
+37f4ad8b4060   ethersphere/bee:2.8.2   "bee start"   6 seconds ago   Up 5 seconds   127.0.0.1:1633->1633/tcp, 0.0.0.0:1634->1634/tcp, :::1634->1634/tcp   bee-1
 ```
 
 And check the logs:
@@ -170,7 +170,7 @@ damage to hardware or loss of funds associated with the Ethereum account connect
 No developers or entity involved will be liable for any claims and damages associated with your use,
 inability to use, or your interaction with other nodes or the software.
 
-"time"="2026-07-07 16:52:59.641444" "level"="info" "logger"="node" "msg"="bee version" "version"="2.8.1-7cf53193"
+"time"="2026-07-07 16:52:59.641444" "level"="info" "logger"="node" "msg"="bee version" "version"="2.8.2-7e703f49"
 "time"="2026-07-07 16:52:59.793257" "level"="info" "logger"="node" "msg"="swarm public key"
 "public_key"="02d8d7e1ca6b3b43653ae27e35a375dd74e3ce2f40587fd264bc7268ed918650ab"
 "time"="2026-07-07 16:53:00.087534" "level"="info" "logger"="node" "msg"="pss public key" "public_key"="02aaae4ede42f47f48aa5182df4b94039ca71254f44ebc5383d5a67f71fe7e6156"

diff --git a/docs/bee/installation/quick-start.md b/docs/bee/installation/quick-start.md
@@ -30,17 +30,17 @@ Run the shell script using `curl` or `wget`:
 
 
 :::tip
-We specify `TAG=v2.8.1` to indicate which Bee version to install. You can find available versions in the ["releases" section](https://github.com/ethersphere/bee/releases) of the Bee GitHub repo.
+We specify `TAG=v2.8.2` to indicate which Bee version to install. You can find available versions in the ["releases" section](https://github.com/ethersphere/bee/releases) of the Bee GitHub repo.
 :::
 
 ```bash
-curl -s https://raw.githubusercontent.com/ethersphere/bee/master/install.sh | TAG=v2.8.1 bash
+curl -s https://raw.githubusercontent.com/ethersphere/bee/master/install.sh | TAG=v2.8.2 bash
 ```
 
 OR
 
 ```bash
-wget -q -O - https://raw.githubusercontent.com/ethersphere/bee/master/install.sh | TAG=v2.8.1 bash
+wget -q -O - https://raw.githubusercontent.com/ethersphere/bee/master/install.sh | TAG=v2.8.2 bash
 ```
 
 Verify installation:
@@ -109,7 +109,7 @@ damage to hardware or loss of funds associated with the Ethereum account connect
 No developers or entity involved will be liable for any claims and damages associated with your use,
 inability to use, or your interaction with other nodes or the software.
 
-"time"="2026-07-07 16:52:59.641444" "level"="info" "logger"="node" "msg"="bee version" "version"="2.8.1-7cf53193"
+"time"="2026-07-07 16:52:59.641444" "level"="info" "logger"="node" "msg"="bee version" "version"="2.8.2-7e703f49"
 "time"="2026-07-07 16:52:59.793257" "level"="info" "logger"="node" "msg"="swarm public key"
 "public_key"="02d8d7e1ca6b3b43653ae27e35a375dd74e3ce2f40587fd264bc7268ed918650ab"
 "time"="2026-07-07 16:53:00.087534" "level"="info" "logger"="node" "msg"="pss public key" "public_key"="02aaae4ede42f47f48aa5182df4b94039ca71254f44ebc5383d5a67f71fe7e6156"
@@ -181,7 +181,7 @@ swarm-cli status
 ```bash
 Bee
 API: http://localhost:1633 [OK]
-Version: 2.8.1-7cf53193
+Version: 2.8.2-7e703f49
 Mode: light
 
 Chainsync
@@ -211,7 +211,7 @@ swarm-cli status
 ```bash
 Bee
 API: http://localhost:1633 [OK]
-Version: 2.8.1-7cf53193
+Version: 2.8.2-7e703f49
 Mode: light
 
 Chainsync

diff --git a/docs/bee/installation/shell-script.md b/docs/bee/installation/shell-script.md
@@ -26,7 +26,7 @@ Below is a step-by-step guide for installing and setting up your Bee node using
 Run the install shell script using either `curl` or `wget`:
 
 :::caution
-In the example below, the version is specified using `TAG=v2.8.1`. Check the [latest Bee releases](https://github.com/ethersphere/bee/tags) and if needed, update the command to install the most recent version (note that in tags containing "rc," the abbreviation stands for "release candidate", and these versions should be used for testing purposes only). 
+In the example below, the version is specified using `TAG=v2.8.2`. Check the [latest Bee releases](https://github.com/ethersphere/bee/tags) and if needed, update the command to install the most recent version (note that in tags containing "rc," the abbreviation stands for "release candidate", and these versions should be used for testing purposes only). 
 :::
 
 :::info
@@ -59,15 +59,15 @@ values={[
 <TabItem value="curl">
 
 ```bash
-curl -s https://raw.githubusercontent.com/ethersphere/bee/master/install.sh | TAG=v2.8.1 bash
+curl -s https://raw.githubusercontent.com/ethersphere/bee/master/install.sh | TAG=v2.8.2 bash
 ```
 </TabItem>
 <TabItem value="wget">
 
 **wget**
 
 ```bash
-wget -q -O - https://raw.githubusercontent.com/ethersphere/bee/master/install.sh | TAG=v2.8.1 bash
+wget -q -O - https://raw.githubusercontent.com/ethersphere/bee/master/install.sh | TAG=v2.8.2 bash
 ```
 </TabItem>
 

diff --git a/docs/bee/working-with-bee/bee-api.md b/docs/bee/working-with-bee/bee-api.md
@@ -584,8 +584,8 @@ curl -s http://localhost:1633/health | jq
 ```json
 {
   "status": "ok",
-  "version": "2.8.1-7cf53193",
-  "apiVersion": "8.1.0"
+  "version": "2.8.2-7e703f49",
+  "apiVersion": "8.1.1"
 }
 ```
 

diff --git a/docs/bee/working-with-bee/staking.md b/docs/bee/working-with-bee/staking.md
@@ -481,13 +481,13 @@ curl -s http://localhost:1633/health | jq
 
 To confirm a successful update, check that the value for the `"version"` field in the results corresponds to the version number of the [latest](https://github.com/ethersphere/bee/releases/latest) Bee release. 
 
-For example, if the latest version was 2.8.1, it would look like this:
+For example, if the latest version was 2.8.2, it would look like this:
 
 ```json
 {
   "status": "ok",
-  "version": "2.8.1-7cf53193",
-  "apiVersion": "8.1.0"
+  "version": "2.8.2-7e703f49",
+  "apiVersion": "8.1.1"
 }
 ```
 

diff --git a/docs/bee/working-with-bee/upgrade.md b/docs/bee/working-with-bee/upgrade.md
@@ -23,11 +23,17 @@ The minimum supported version is currently **v2.8.0**, the release that introduc
 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.1 is **non-disruptive for nodes already on v2.8.0**: it makes no breaking p2p protocol changes, so you can upgrade in place using the steps below.
+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.
 
 :::warning
-**If you are running Bee v2.6.0 or older:** Bee v2.8.1 removes the last of the v2.6.0 backward-compatibility code, so you cannot upgrade to it directly.
-Either upgrade stepwise (**v2.6.0 → v2.8.0 → v2.8.1**) so the data migrations run, or reinstall the node fresh on v2.8.1.
+**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.
+:::
+
+:::info
+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](https://github.com/ethersphere/bee/releases/tag/v2.8.2).
+With tracing disabled, nothing changes.
 :::
 
 
@@ -46,26 +52,38 @@ sudo apt-get update
 sudo apt-get upgrade bee
 ```
 
-And will see output like this after a successful upgrade:
-```
-Reading package lists... Done
-Building dependency tree
-Reading state information... Done
-Calculating upgrade... Done
+You will see output like this after a successful upgrade:
+
+```text
 The following packages will be upgraded:
   bee
 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
-Need to get 0 B/27.2 MB of archives.
-After this operation, 73.7 kB of additional disk space will be used.
-Do you want to continue? [Y/n] Y
-(Reading database ... 103686 files and directories currently installed.)
-Preparing to unpack .../archives/bee_2.0.0_amd64.deb ...
-Unpacking bee (2.0.0) over (1.17.3) ...
-Setting up bee (2.0.0) ...
-Installing new version of config file /etc/default/bee ...
+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:
+
+```text
+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] ?
 ```
 
-Make sure to pay attention to any prompts, read them carefully, and respond to them with your preference.
+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:
 
@@ -76,6 +94,7 @@ 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](../installation/shell-script.md), you can replace the binary by running the script again with the new version's `TAG`.
 
 ### Docker