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.
|