fix: add maxLength: 65536 to body/content fields to exempt from SM-IS-01 10 KB cap#45826
Conversation
…-01 10 KB cap Fixes the SM-IS-01 maxLength exemption gap across all affected tools. The mcp_scripts_validation.cjs logic skips fields with an explicit maxLength, so fields without one were subject to the 10 KB global cap. Fields updated in both pkg/workflow/js/safe_outputs_tools.json and actions/setup/js/safe_outputs_tools.json: - update_discussion.body - update_issue.body - update_pull_request.body - update_release.body - update_project.draft_body - create_pull_request.body - create_pull_request_review_comment.body - submit_pull_request_review.body - reply_to_pull_request_review_comment.body - close_discussion.body - close_issue.body - close_pull_request.body - create_agent_session.body - create_project_status_update.body - create_check_run.summary, text - autofix_code_scanning_alert.fix_description, fix_code - merge_pull_request.commit_message - push_to_pull_request_branch.message - dismiss_pull_request_review.justification - noop.message - report_incomplete.details Closes #44842 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Adds explicit large-content limits to safe-output tool schemas, bypassing the global 10 KB validation cap.
Changes:
- Adds
maxLength: 65536to 23 content fields. - Synchronizes compiler and runtime schema catalogs.
Show a summary per file
| File | Description |
|---|---|
pkg/workflow/js/safe_outputs_tools.json |
Updates compiler-embedded schemas. |
actions/setup/js/safe_outputs_tools.json |
Updates runtime schemas. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/2 changed files
- Comments generated: 2
- Review effort level: Medium
|
@copilot please run the
|
…ing reason exemption Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Addressed unresolved feedback in
I couldn’t query/retrigger PR checks from this environment due GitHub API 403 on |
|
@copilot please run the
|
Handled the unresolved Copilot threads newest-first and replied on both review comments ( |
|
@copilot please run the
|
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Done in |
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
…CP test Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Fixed in
|
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Fixed in I updated Validated with:
|
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Fixed in I updated the failing AWF digest tests in
Validated with:
|
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Fixed in I investigated run Validated with targeted tests:
|
The SM-IS-01 validation in
mcp_scripts_validation.cjsenforces a 10 KB global cap on all string fields unless they have an explicitmaxLength(which delegates enforcement to the API layer).create_issue.body,create_discussion.body, andadd_comment.bodywere already exempted viamaxLength: 65536(#43867), but 23 large-content fields across 21 tools were still being capped at 10 KB.Changes
maxLength: 65536to all affected fields in bothpkg/workflow/js/safe_outputs_tools.jsonandactions/setup/js/safe_outputs_tools.json(files are kept in sync):update_discussion,update_issue,update_pull_request,update_releasebodycreate_pull_request,close_discussion,close_issue,close_pull_requestbodycreate_pull_request_review_comment,submit_pull_request_review,reply_to_pull_request_review_commentbodycreate_agent_session,create_project_status_updatebodyupdate_projectdraft_bodycreate_check_runsummary,textautofix_code_scanning_alertfix_description,fix_codemerge_pull_requestcommit_messagepush_to_pull_request_branchmessagedismiss_pull_request_reviewjustificationnoopmessagereport_incompletedetails