Release 2.20.1.

Signed-off-by: Thomas Hallgren <[email protected]>

Makefile

@@ -8,7 +8,7 @@ telepresence-remote:
 .PHONY: telepresence-remote
 
 # MATCH_TAGS is the regexp matching the tags that we expect will have docs.
-MATCH_TAGS ?= ^v2\.[2-9][0-9]+\.[0-9]+(-(rc)\.[0-9]+)?$$
+MATCH_TAGS ?= ^v2\.[2-9][0-9]+\.[0-9]+$$
 
 # EXCLUDE_TAGS is used when we want to exclude some of the matching tags from the telepresence repository
 EXCLUDE_TAGS ?=

versioned_docs/version-2.20/install/manager.md

@@ -5,7 +5,7 @@ hide_table_of_contents: true
 
 # Install/Uninstall the Traffic Manager
 
-Telepresence uses a traffic manager to send/recieve cloud traffic to the user. Telepresence uses [Helm](https://helm.sh) under the hood to install the traffic manager in your cluster. The `telepresence` binary embeds both `helm` and a helm-chart for a traffic-manager that is of the same version as the binary.
+Telepresence uses a traffic manager to send/receive cloud traffic to the user. Telepresence uses [Helm](https://helm.sh) under the hood to install the traffic manager in your cluster. The `telepresence` binary embeds both `helm` and a helm-chart for a traffic-manager that is of the same version as the binary.
 
 ## Prerequisites
 

versioned_docs/version-2.20/release-notes.md

@@ -1,6 +1,19 @@
 
 [comment]: # (Code generated by relnotesgen. DO NOT EDIT.)
 # <img src="images/logo.png" height="64px"/> Telepresence Release Notes
+## Version 2.20.1 <span style="font-size: 16px;">(October 10)</span>
+## <div style="display:flex;"><img src="images/bugfix.png" alt="bugfix" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">Some workloads missing in the telepresence list output (typically replicasets owned by rollouts).</div></div>
+<div style="margin-left: 15px">
+
+-> 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.
+</div>
+
+## <div style="display:flex;"><img src="images/bugfix.png" alt="bugfix" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">Allow comma separated list of daemons for the gather-logs command.</div></div>
+<div style="margin-left: 15px">
+
+-> 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`.
+</div>
+
 ## Version 2.20.0 <span style="font-size: 16px;">(October  3)</span>
 ## <div style="display:flex;"><img src="images/feature.png" alt="feature" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">Add timestamp to telepresence_logs.zip filename.</div></div>
 <div style="margin-left: 15px">
@@ -66,7 +79,7 @@ A <code>telepresence connect --docker</code> failed when attempting to connect t
 ## <div style="display:flex;"><img src="images/feature.png" alt="feature" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">[Add brew support for the OSS version of Telepresence.](https://github.com/telepresenceio/telepresence/issues/3609)</div></div>
 <div style="margin-left: 15px">
 
-The Open-Source Software version of Telepresence can now be installed using the brew formula via <code>brew install datawire/blackbird/telepresence-oss</code>.
+The Open-Source Software version of Telepresence can now be installed using the brew formula via <code>brew install telepresenceio/telepresence/telepresence-oss</code>.
 </div>
 
 ## <div style="display:flex;"><img src="images/feature.png" alt="feature" style="width:30px;height:fit-content;"/><div style="display:flex;margin-left:7px;">Add --create-namespace flag to the telepresence helm install command.</div></div>

versioned_docs/version-2.20/release-notes.mdx

@@ -7,6 +7,15 @@ import { Note, Title, Body } from '@site/src/components/ReleaseNotes'
 [comment]: # (Code generated by relnotesgen. DO NOT EDIT.)
 
 # Telepresence Release Notes
+## Version 2.20.1 <span style={{fontSize:'16px'}}>(October 10)</span>
+<Note>
+	<Title type="bugfix">Some workloads missing in the telepresence list output (typically replicasets owned by rollouts).</Title>
+	<Body>-> 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.</Body>
+</Note>
+<Note>
+	<Title type="bugfix">Allow comma separated list of daemons for the gather-logs command.</Title>
+	<Body>-> 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`.</Body>
+</Note>
 ## Version 2.20.0 <span style={{fontSize:'16px'}}>(October  3)</span>
 <Note>
 	<Title type="feature">Add timestamp to telepresence_logs.zip filename.</Title>
@@ -51,7 +60,7 @@ import { Note, Title, Body } from '@site/src/components/ReleaseNotes'
 ## Version 2.19.1 <span style={{fontSize:'16px'}}>(July 12)</span>
 <Note>
 	<Title type="feature" docs="https://github.com/telepresenceio/telepresence/issues/3609">Add brew support for the OSS version of Telepresence.</Title>
-	<Body>The Open-Source Software version of Telepresence can now be installed using the brew formula via <code>brew install datawire/blackbird/telepresence-oss</code>.</Body>
+	<Body>The Open-Source Software version of Telepresence can now be installed using the brew formula via <code>brew install telepresenceio/telepresence/telepresence-oss</code>.</Body>
 </Note>
 <Note>
 	<Title type="feature">Add --create-namespace flag to the telepresence helm install command.</Title>

versioned_docs/version-2.20/variables.yml

@@ -1,2 +1,2 @@
-version: "2.20.0"
-dlVersion: "v2.20.0"
+version: "2.20.1"
+dlVersion: "v2.20.1"