From e83c5c17ef2557da4ef0b6934852906b8fa16aab Mon Sep 17 00:00:00 2001 From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com> Date: Thu, 29 Feb 2024 12:40:01 -0500 Subject: [PATCH] docs: Update 0.15.x release notes (#4460) --- website/content/docs/release-notes/v0_15_0.mdx | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/website/content/docs/release-notes/v0_15_0.mdx b/website/content/docs/release-notes/v0_15_0.mdx index 3c4cb57638..251f5f0d41 100644 --- a/website/content/docs/release-notes/v0_15_0.mdx +++ b/website/content/docs/release-notes/v0_15_0.mdx @@ -7,7 +7,7 @@ description: |- # Boundary 0.15.0 release notes -**GA date:** January 30, 2023 +**GA date:** January 30, 2024 @include 'release-notes/intro.mdx' @@ -181,14 +181,18 @@ description: |- 0.15.0 +

+ (Fixed in 0.15.1) Maximum number of connections allowed is incorrect - A known issue causes Boundary to permit one less than the allowed number of connections that you configured for a given target. For example, if you configured the session connection limit for a target at 2, Boundary only permits 1 connection to the target. If the value is 1, Boundary does not allow any connections to the target. + A known issue causes Boundary to permit one less than the allowed number of connections that you configured for a given target. For example, if you configured the session connection limit for a target at 2, Boundary only permits 1 connection to the target. If the value is 1, Boundary does not allow any connections to the target. A value of -1 still means that connections to the target are unlimited. +

+ This issue is fixed in version 0.15.1.

- This is a known issue that will be fixed in an upcoming release. A value of -1 still means that connections to the target are unlimited. + Upgrade to the latest version of Boundary

Learn more:  Refer to the CLI docs for information about using targets create or targets update to configure a maximum number of connections.