From 4f9f28139829d72b1e065e29f612df54e38f9f26 Mon Sep 17 00:00:00 2001 From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com> Date: Thu, 21 Nov 2024 17:44:39 -0500 Subject: [PATCH] docs: Add resolved issue to release notes (#5260) * docs: Add resolved issue to release notes * Update website/content/docs/release-notes/v0_18_0.mdx Co-authored-by: Johan Brandhorst-Satzkorn * docs: Revise gerund for standards --------- Co-authored-by: Johan Brandhorst-Satzkorn --- website/content/docs/release-notes/v0_18_0.mdx | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/website/content/docs/release-notes/v0_18_0.mdx b/website/content/docs/release-notes/v0_18_0.mdx index 2aa389c90a..20f084b0c0 100644 --- a/website/content/docs/release-notes/v0_18_0.mdx +++ b/website/content/docs/release-notes/v0_18_0.mdx @@ -168,5 +168,23 @@ description: |- + + + 0.18.0 (Fixed in 0.18.1) + + + Users are incorrectly removed from managed groups + + + If your organization has over 10,000 managed groups, Boundary may incorrectly remove users from the managed group memberships. +

+ In version 0.18.0 and earlier, there was a maximum number of managed groups supported for an auth method. If you had over 10,000 managed groups, Boundary may have incorrectly removed a user from a group during authentication. This issue is fixed in version 0.18.1. There is no longer a maximum number of managed groups. +

+ Learn more:  Managed groups +

+ Upgrade to the latest version of Boundary + + + \ No newline at end of file