From e8518764c21d5b272f67d05a1ffcd6f504fb3ea8 Mon Sep 17 00:00:00 2001
From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com>
Date: Thu, 8 May 2025 13:22:16 -0400
Subject: [PATCH] docs: Update release notes (#5708)
* docs: Update release notes
* docs: Add new known issue
* docs: Update known issue
---
.../content/docs/release-notes/v0_17_0.mdx | 18 ++++++
.../content/docs/release-notes/v0_18_0.mdx | 18 ++++++
.../content/docs/release-notes/v0_19_0.mdx | 58 +++++++++++++++++++
3 files changed, 94 insertions(+)
diff --git a/website/content/docs/release-notes/v0_17_0.mdx b/website/content/docs/release-notes/v0_17_0.mdx
index 22d6e77a6..e5072f0d3 100644
--- a/website/content/docs/release-notes/v0_17_0.mdx
+++ b/website/content/docs/release-notes/v0_17_0.mdx
@@ -309,6 +309,24 @@ description: >-
+
+
+ 0.17.0 - 0.17.4
+
+ (Fixed in Boundary Enterprise and HCP Boundary 0.17.5)
+ |
+
+ Canceled SSH connections cause performance issues
+ |
+
+ When an SSH connection was canceled, it could cause a spike in CPU usage. In some cases, egress workers become unresponsive, leading to performance issues. The issue occurred when the connection context was canceled at specific times in the process, creating a busy loop that prevented workers from completing tasks.
+
+ This issue is resolved in Boundary Enterprise and HCP Boundary version 0.17.5. Workers no longer end up in a busy loop when SSH connections are canceled.
+
+ Upgrade to the latest version of Boundary
+ |
+
+
\ No newline at end of file
diff --git a/website/content/docs/release-notes/v0_18_0.mdx b/website/content/docs/release-notes/v0_18_0.mdx
index 465ba1610..daffdaeab 100644
--- a/website/content/docs/release-notes/v0_18_0.mdx
+++ b/website/content/docs/release-notes/v0_18_0.mdx
@@ -326,5 +326,23 @@ description: >-
+
+
+ 0.17.0 - 0.18.3
+
+ (Fixed in Boundary Enterprise and HCP Boundary 0.18.4)
+ |
+
+ Canceled SSH connections cause performance issues
+ |
+
+ When an SSH connection was canceled, it could cause a spike in CPU usage. In some cases, egress workers become unresponsive, leading to performance issues. The issue occurred when the connection context was canceled at specific times in the process, creating a busy loop that prevented workers from completing tasks.
+
+ This issue is resolved in Boundary Enterprise and HCP Boundary version 0.18.4. Workers no longer end up in a busy loop when SSH connections are canceled.
+
+ Upgrade to the latest version of Boundary
+ |
+
+
\ No newline at end of file
diff --git a/website/content/docs/release-notes/v0_19_0.mdx b/website/content/docs/release-notes/v0_19_0.mdx
index 31c80b1a7..086d73a86 100644
--- a/website/content/docs/release-notes/v0_19_0.mdx
+++ b/website/content/docs/release-notes/v0_19_0.mdx
@@ -228,6 +228,64 @@ description: >-
However, soft-deleted users were not being properly restored when they logged back in and it affected search capabilities.
This issue is resolved in version 0.19.1. Soft-deleted users are now properly restored as active when they log in again if the refresh token is less than 20 days old.
+
+ Upgrade to the latest version of Boundary
+
+
+
+
+
+ 0.17.0 - 0.19.0
+
+ (Fixed in 0.19.2)
+ |
+
+ Canceled SSH connections cause performance issues
+ |
+
+ When an SSH connection was canceled, it could cause a spike in CPU usage. In some cases, egress workers become unresponsive, leading to performance issues. The issue occurred when the connection context was canceled at specific times in the process, creating a busy loop that prevented workers from completing tasks.
+
+ This issue is resolved in version 0.19.2. Workers no longer enter a busy loop when SSH connections are canceled.
+
+ Upgrade to the latest version of Boundary
+ |
+
+
+
+
+ 0.19.0
+
+ (Fixed in 0.19.2)
+ |
+
+ Unable to change key type for Vault SSH certificate credential library using the UI
+ |
+
+ When you attempted to change the key type for a Vault SSH certificate credential library using the UI, the update failed.
+
+ This issue is resolved in version 0.19.2. You can now change the key type using the UI.
+
+ Upgrade to the latest version of Boundary
+ |
+
+
+
+
+ 0.19.0
+
+ (Fixed in 0.19.2)
+ |
+
+ CVE-2025-22873
+ |
+
+ The version of Go that was used in Boundary release 0.19.x contained a security vulnerability. Although this vulnerability did not affect Boundary, release 0.19.2 was updated to use a new version of Go.
+
+ Learn more:
+
+ CVE-2025-22873
+
+ Upgrade to the latest version of Boundary
|