From d690c7a5b6a35e87d9fae511666963a94e9744a1 Mon Sep 17 00:00:00 2001 From: John Votta Date: Fri, 17 Jul 2026 14:43:02 -0700 Subject: [PATCH] Remove incorrect has_legacy_limits doc comment The comment claimed that adjusting the namespace's capacity resets a Support-set APS limit. That behavior is inaccurate, so remove the stale line. Co-Authored-By: Claude Opus 4.8 (1M context) --- temporal/api/cloud/namespace/v1/message.proto | 1 - 1 file changed, 1 deletion(-) diff --git a/temporal/api/cloud/namespace/v1/message.proto b/temporal/api/cloud/namespace/v1/message.proto index 4b708fd..0a38c5a 100644 --- a/temporal/api/cloud/namespace/v1/message.proto +++ b/temporal/api/cloud/namespace/v1/message.proto @@ -443,7 +443,6 @@ message NamespaceCapacityInfo { string namespace = 1; // Whether the namespace's APS limit was set by Temporal Support. - // When true, adjusting the namespace's capacity will reset this limit. bool has_legacy_limits = 2; // The current capacity of the namespace.