diff --git a/docs/release-notes.md b/docs/release-notes.md
index 48f0c14818..99b2d4c01e 100644
--- a/docs/release-notes.md
+++ b/docs/release-notes.md
@@ -1,17 +1,24 @@
[comment]: # (Code generated by relnotesgen. DO NOT EDIT.)
# 
Telepresence Release Notes
+## Version 2.20.2
+## 
Crash in traffic-manager configured with agentInjector.enabled=false
+
+A traffic-manager that was installed with the Helm value `agentInjector.enabled=false` crashed when a client used the commands `telepresence version` or `telepresence status`. Those commands would call a method on the traffic-manager that panicked if no traffic-agent was present. This method will now instead return the standard `Unavailable` error code, which is expected by the caller.
+
+
## Version 2.20.1 (October 10)
## Some workloads missing in the telepresence list output (typically replicasets owned by rollouts).
--> Version 2.20.0 introduced a regression in the `telepresence list` command, resulting in the omission of all workloads that were owned by another workload. The correct behavior is to just omit those workloads that are owned by the supported workload kinds `Deployment`, `ReplicaSet`, `StatefulSet`, and `Rollout`. Furthermore, the `Rollout` kind must only be considered supported when the Argo Rollouts feature is enabled in the traffic-manager.
+Version 2.20.0 introduced a regression in the `telepresence list` command, resulting in the omission of all workloads that were owned by another workload. The correct behavior is to just omit those workloads that are owned by the supported workload kinds `Deployment`, `ReplicaSet`, `StatefulSet`, and `Rollout`. Furthermore, the `Rollout` kind must only be considered supported when the Argo Rollouts feature is enabled in the traffic-manager.
## Allow comma separated list of daemons for the gather-logs command.
--> The name of the `telepresence gather-logs` flag `--daemons` suggests that the argument can contain more than one daemon, but prior to this fix, it couldn't. It is now possible to use a comma separated list, e.g. `telepresence gather-logs --daemons root,user`.
+The name of the `telepresence gather-logs` flag `--daemons` suggests that the argument can contain more than one daemon, but prior to this fix, it couldn't. It is now possible to use a comma separated list, e.g. `telepresence gather-logs --daemons root,user`.
## Version 2.20.0 (October 3)
diff --git a/docs/release-notes.mdx b/docs/release-notes.mdx
index edb6e90d56..981a01ead9 100644
--- a/docs/release-notes.mdx
+++ b/docs/release-notes.mdx
@@ -7,14 +7,19 @@ import { Note, Title, Body } from '@site/src/components/ReleaseNotes'
[comment]: # (Code generated by relnotesgen. DO NOT EDIT.)
# Telepresence Release Notes
+## Version 2.20.2
+
+ Crash in traffic-manager configured with agentInjector.enabled=false
+ A traffic-manager that was installed with the Helm value `agentInjector.enabled=false` crashed when a client used the commands `telepresence version` or `telepresence status`. Those commands would call a method on the traffic-manager that panicked if no traffic-agent was present. This method will now instead return the standard `Unavailable` error code, which is expected by the caller.
+
## Version 2.20.1 (October 10)
Some workloads missing in the telepresence list output (typically replicasets owned by rollouts).
- -> Version 2.20.0 introduced a regression in the `telepresence list` command, resulting in the omission of all workloads that were owned by another workload. The correct behavior is to just omit those workloads that are owned by the supported workload kinds `Deployment`, `ReplicaSet`, `StatefulSet`, and `Rollout`. Furthermore, the `Rollout` kind must only be considered supported when the Argo Rollouts feature is enabled in the traffic-manager.
+ Version 2.20.0 introduced a regression in the `telepresence list` command, resulting in the omission of all workloads that were owned by another workload. The correct behavior is to just omit those workloads that are owned by the supported workload kinds `Deployment`, `ReplicaSet`, `StatefulSet`, and `Rollout`. Furthermore, the `Rollout` kind must only be considered supported when the Argo Rollouts feature is enabled in the traffic-manager.
Allow comma separated list of daemons for the gather-logs command.
- -> The name of the `telepresence gather-logs` flag `--daemons` suggests that the argument can contain more than one daemon, but prior to this fix, it couldn't. It is now possible to use a comma separated list, e.g. `telepresence gather-logs --daemons root,user`.
+ The name of the `telepresence gather-logs` flag `--daemons` suggests that the argument can contain more than one daemon, but prior to this fix, it couldn't. It is now possible to use a comma separated list, e.g. `telepresence gather-logs --daemons root,user`.
## Version 2.20.0 (October 3)
diff --git a/go.mod b/go.mod
index 97d2f2f0b8..b58aa4e76a 100644
--- a/go.mod
+++ b/go.mod
@@ -36,7 +36,7 @@ require (
github.com/spf13/cobra v1.8.1
github.com/spf13/pflag v1.0.5
github.com/stretchr/testify v1.9.0
- github.com/telepresenceio/telepresence/rpc/v2 v2.20.1
+ github.com/telepresenceio/telepresence/rpc/v2 v2.20.2-rc.0
github.com/vishvananda/netlink v1.3.0
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.55.0
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.55.0
diff --git a/pkg/vif/testdata/router/go.mod b/pkg/vif/testdata/router/go.mod
index 2b8329a50c..86ab4fe14e 100644
--- a/pkg/vif/testdata/router/go.mod
+++ b/pkg/vif/testdata/router/go.mod
@@ -51,7 +51,7 @@ require (
github.com/rogpeppe/go-internal v1.12.0 // indirect
github.com/spf13/cobra v1.8.1 // indirect
github.com/spf13/pflag v1.0.5 // indirect
- github.com/telepresenceio/telepresence/rpc/v2 v2.20.1 // indirect
+ github.com/telepresenceio/telepresence/rpc/v2 v2.20.2-rc.0 // indirect
github.com/vishvananda/netlink v1.3.0 // indirect
github.com/vishvananda/netns v0.0.4 // indirect
github.com/x448/float16 v0.8.4 // indirect