From a547f51407f143fcf7edce0243380faf62eae0aa Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 7 Jul 2026 02:28:39 +0000 Subject: [PATCH 1/2] Initial plan From 357562d55f3f76e4a583d8c6a40881dba9d59c68 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 7 Jul 2026 02:44:38 +0000 Subject: [PATCH 2/2] fix: add maxLength: 65536 to create_issue and create_discussion body fields The SM-IS-01 global string-length cap (10 KB) is bypassed for any field with an explicit maxLength in the schema. add_comment.body correctly has maxLength: 65536 and is exempt. This commit adds the same maxLength to create_discussion.body and create_issue.body so they are also exempt from the 10 KB cap and deferred to handler-level (GitHub API) enforcement. Also removes the "Maximum 10 KB" guidance from create_discussion.body description, which described the accidental cap, not an intended limit. Fixes #43867 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- actions/setup/js/safe_outputs_tools.json | 4 +++- pkg/workflow/js/safe_outputs_tools.json | 4 +++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/actions/setup/js/safe_outputs_tools.json b/actions/setup/js/safe_outputs_tools.json index 789b3387ded..9e0d5a3699c 100644 --- a/actions/setup/js/safe_outputs_tools.json +++ b/actions/setup/js/safe_outputs_tools.json @@ -13,6 +13,7 @@ "body": { "type": "string", "minLength": 20, + "maxLength": 65536, "description": "Detailed issue description in Markdown. Must be the final intended body \u2014 not a placeholder or test value. Do NOT repeat the title as a heading since it already appears as the issue's h1. Include context, reproduction steps, or acceptance criteria as appropriate." }, "labels": { @@ -99,7 +100,8 @@ }, "body": { "type": "string", - "description": "Discussion content in Markdown. Do NOT repeat the title as a heading since it already appears as the discussion's h1. Include all relevant context, findings, or questions. Maximum 10 KB (10240 bytes). If your content is larger, trim it, link to an external artifact (for example a gist), or upload content via upload_asset instead of inlining." + "maxLength": 65536, + "description": "Discussion content in Markdown. Do NOT repeat the title as a heading since it already appears as the discussion's h1. Include all relevant context, findings, or questions." }, "category": { "type": "string", diff --git a/pkg/workflow/js/safe_outputs_tools.json b/pkg/workflow/js/safe_outputs_tools.json index 789b3387ded..9e0d5a3699c 100644 --- a/pkg/workflow/js/safe_outputs_tools.json +++ b/pkg/workflow/js/safe_outputs_tools.json @@ -13,6 +13,7 @@ "body": { "type": "string", "minLength": 20, + "maxLength": 65536, "description": "Detailed issue description in Markdown. Must be the final intended body \u2014 not a placeholder or test value. Do NOT repeat the title as a heading since it already appears as the issue's h1. Include context, reproduction steps, or acceptance criteria as appropriate." }, "labels": { @@ -99,7 +100,8 @@ }, "body": { "type": "string", - "description": "Discussion content in Markdown. Do NOT repeat the title as a heading since it already appears as the discussion's h1. Include all relevant context, findings, or questions. Maximum 10 KB (10240 bytes). If your content is larger, trim it, link to an external artifact (for example a gist), or upload content via upload_asset instead of inlining." + "maxLength": 65536, + "description": "Discussion content in Markdown. Do NOT repeat the title as a heading since it already appears as the discussion's h1. Include all relevant context, findings, or questions." }, "category": { "type": "string",