From e59461907351e084eeb3d19e1ebc230e719c483a Mon Sep 17 00:00:00 2001 From: Stephan Behnke Date: Thu, 16 Jul 2026 11:04:11 -0700 Subject: [PATCH] Make standalone_nexus_operation capability optional for field presence Change NamespaceInfo.Capabilities.standalone_nexus_operation from an implicit-presence bool to `optional bool` so clients can distinguish "server does not know this capability" (field absent) from "server supports it but it is disabled" (field present, false). Wire-compatible; regenerated Go bindings change the field to *bool. Co-Authored-By: Claude Opus 4.8 (1M context) --- temporal/api/namespace/v1/message.proto | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/temporal/api/namespace/v1/message.proto b/temporal/api/namespace/v1/message.proto index 2dbca4710..2c051ef3f 100644 --- a/temporal/api/namespace/v1/message.proto +++ b/temporal/api/namespace/v1/message.proto @@ -53,7 +53,7 @@ message NamespaceInfo { // True if the namespace supports worker commands (server-to-worker communication via control queues). bool worker_commands = 10; // True if the namespace supports standalone Nexus operations. - bool standalone_nexus_operation = 11; + optional bool standalone_nexus_operation = 11; // True if the namespace supports attaching callbacks on workflow updates bool workflow_update_callbacks = 12; // When true, workers should use poller autoscaling by default unless explicitly configured otherwise.