Upgrade gh-aw to v0.39.0 and recompile workflows

[Copilot]

Upgraded GitHub Agentic Workflows to v0.39.0 and regenerated all workflow lock files.

Version Updates

• gh-aw: v0.38.5 → v0.39.0
• Copilot CLI: 0.0.399 → 0.0.400
• MCP Gateway: v0.0.84 → v0.0.86
• Action SHA: 10f1341b529f9a8b51c463e191b7dd63d4caccfd

Changes

• Recompiled 11 workflow lock files with updated templates
• Updated agentics-maintenance.yml auto-generated workflow
• Code optimization in v0.39.0 reduced lock file size by 429 lines (967 deletions, 538 insertions)

Expected Warning

One informational warning: web-search tool not supported by copilot engine in update-docs.md workflow. Does not affect functionality.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

This pull request upgrades the gh-aw (GitHub Agentic Workflows) tooling from v0.38.5 to v0.39.0 and recompiles all workflow lock files with the new version. The upgrade includes updates to Copilot CLI (0.0.399 → 0.0.400) and MCP Gateway (v0.0.84 → v0.0.86), along with systematic changes to workflow configurations and formatting.

Changes:

• Updated gh-aw version references from v0.38.5 to v0.39.0 across all workflow files
• Upgraded Copilot CLI from 0.0.399 to 0.0.400 and MCP Gateway from v0.0.84 to v0.0.86
• Refactored threat detection template to use function calls instead of inline content
• Added new instruction for using the "noop" tool but removed "noop" configuration from safe outputs handlers
• Applied formatting changes including trailing whitespace additions and YAML indentation adjustments

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 11 comments.

Show a summary per file

File	Description
.github/workflows/weekly-research.lock.yml	Updated versions, refactored threat detection, removed noop config despite adding noop instruction
.github/workflows/update-docs.lock.yml	Updated versions, refactored threat detection, removed noop config despite adding noop instruction
.github/workflows/pr-fix.lock.yml	Updated versions, refactored threat detection, removed noop config despite adding noop instruction
.github/workflows/issue-triage.lock.yml	Updated versions, refactored threat detection, removed noop config despite adding noop instruction
.github/workflows/daily-test-improver.lock.yml	Updated versions, refactored threat detection, removed noop config despite adding noop instruction
.github/workflows/daily-qa.lock.yml	Updated versions, refactored threat detection, removed noop config despite adding noop instruction
.github/workflows/daily-progress.lock.yml	Updated versions, refactored threat detection, removed noop config despite adding noop instruction
.github/workflows/daily-plan.lock.yml	Updated versions, refactored threat detection, removed noop config despite adding noop instruction
.github/workflows/daily-perf-improver.lock.yml	Updated versions, refactored threat detection, removed noop config despite adding noop instruction
.github/workflows/ci-doctor.lock.yml	Updated versions, refactored threat detection, removed noop config despite adding noop instruction
.github/workflows/audit-workflows.lock.yml	Updated versions, refactored threat detection, removed noop config despite adding noop instruction
.github/workflows/agentics-maintenance.yml	Updated gh-aw version reference to v0.39.0

[Copilot]

The noop configuration has been removed from the GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG in this workflow. However, the workflow now includes an instruction for agents to call the "noop" tool (line 586): "Note: If you made no other safe output tool calls during this workflow execution, call the 'noop' tool to provide a status message indicating completion or that no actions were needed."

This creates an inconsistency: the workflow instructs users to call the "noop" tool, but the safe outputs handler configuration no longer includes the noop handler (line 1159). This means if the agent follows the instruction and calls the noop tool, it may not be processed correctly.

Either the noop configuration should be restored, or the instruction about calling the noop tool should be removed to maintain consistency.

Suggested change

	GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":1,\"target\":\"*\"},\"create_discussion\":{\"category\":\"agentic-workflows\",\"expires\":168,\"max\":5,\"title_prefix\":\"${{ github.workflow }}\"},\"create_pull_request\":{\"base_branch\":\"${{ github.ref_name }}\",\"draft\":true,\"max\":1,\"max_patch_size\":1024},\"missing_data\":{},\"missing_tool\":{}}"
	GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":1,\"target\":\"*\"},\"create_discussion\":{\"category\":\"agentic-workflows\",\"expires\":168,\"max\":5,\"title_prefix\":\"${{ github.workflow }}\"},\"create_pull_request\":{\"base_branch\":\"${{ github.ref_name }}\",\"draft\":true,\"max\":1,\"max_patch_size\":1024},\"missing_data\":{},\"missing_tool\":{},\"noop\":{}}"

[Copilot]

The noop configuration has been removed from the GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG in this workflow. However, the workflow now includes an instruction for agents to call the "noop" tool (line 605): "Note: If you made no other safe output tool calls during this workflow execution, call the 'noop' tool to provide a status message indicating completion or that no actions were needed."

This creates an inconsistency: the workflow instructs users to call the "noop" tool, but the safe outputs handler configuration no longer includes the noop handler (line 1141). This means if the agent follows the instruction and calls the noop tool, it may not be processed correctly.

Either the noop configuration should be restored, or the instruction about calling the noop tool should be removed to maintain consistency.

Suggested change

	GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":3},\"create_discussion\":{\"category\":\"agentic-workflows\",\"close_older_discussions\":true,\"expires\":168,\"max\":1,\"title_prefix\":\"${{ github.workflow }}\"},\"create_issue\":{\"max\":5,\"title_prefix\":\"${{ github.workflow }}\"},\"missing_data\":{},\"missing_tool\":{}}"
	GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":3},\"create_discussion\":{\"category\":\"agentic-workflows\",\"close_older_discussions\":true,\"expires\":168,\"max\":1,\"title_prefix\":\"${{ github.workflow }}\"},\"create_issue\":{\"max\":5,\"title_prefix\":\"${{ github.workflow }}\"},\"missing_data\":{},\"missing_tool\":{},\"noop\":{}}"

[Copilot]

The noop configuration has been removed from the GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG in this workflow. However, the PR description states that a new instruction was added: "Note: If you made no other safe output tool calls during this workflow execution, call the 'noop' tool to provide a status message indicating completion or that no actions were needed."

This creates an inconsistency: the workflow now instructs users to call the "noop" tool (line 489), but the safe outputs handler configuration no longer includes the noop handler (line 1009). This means if the agent follows the instruction and calls the noop tool, it may not be processed correctly.

Either the noop configuration should be restored, or the instruction about calling the noop tool should be removed to maintain consistency.

Suggested change

	GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"create_discussion\":{\"category\":\"agentic-workflows\",\"expires\":168,\"max\":1,\"title_prefix\":\"${{ github.workflow }}\"},\"missing_data\":{},\"missing_tool\":{}}"
	GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"create_discussion\":{\"category\":\"agentic-workflows\",\"expires\":168,\"max\":1,\"title_prefix\":\"${{ github.workflow }}\"},\"missing_data\":{},\"missing_tool\":{},\"noop\":{}}"

[Copilot]

The noop configuration has been removed from the GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG in this workflow. However, the workflow now includes an instruction for agents to call the "noop" tool (line 524): "Note: If you made no other safe output tool calls during this workflow execution, call the 'noop' tool to provide a status message indicating completion or that no actions were needed."

This creates an inconsistency: the workflow instructs users to call the "noop" tool, but the safe outputs handler configuration no longer includes the noop handler (line 1085). This means if the agent follows the instruction and calls the noop tool, it may not be processed correctly.

Either the noop configuration should be restored, or the instruction about calling the noop tool should be removed to maintain consistency.

Suggested change

	GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":1},\"add_labels\":{\"max\":5},\"missing_data\":{},\"missing_tool\":{}}"
	GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":1},\"add_labels\":{\"max\":5},\"noop\":{},\"missing_data\":{},\"missing_tool\":{}}"

[Copilot]

The noop configuration has been removed from the GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG in this workflow. However, the workflow now includes an instruction for agents to call the "noop" tool (line 658): "Note: If you made no other safe output tool calls during this workflow execution, call the 'noop' tool to provide a status message indicating completion or that no actions were needed."

This creates an inconsistency: the workflow instructs users to call the "noop" tool, but the safe outputs handler configuration no longer includes the noop handler (line 1231). This means if the agent follows the instruction and calls the noop tool, it may not be processed correctly.

Either the noop configuration should be restored, or the instruction about calling the noop tool should be removed to maintain consistency.

Suggested change

GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":1,\"target\":\"*\"},\"create_discussion\":{\"category\":\"agentic-workflows\",\"expires\":168,\"max\":1,\"title_prefix\":\"${{ github.workflow }}\"},\"create_issue\":{\"max\":1},\"create_pull_request\":{\"base_branch\":\"${{ github.ref_name }}\",\"draft\":true,\"max\":1,\"max_patch_size\":1024},\"missing_data\":{},\"missing_tool\":{}}"

GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":1,\"target\":\"*\"},\"create_discussion\":{\"category\":\"agentic-workflows\",\"expires\":168,\"max\":1,\"title_prefix\":\"${{ github.workflow }}\"},\"create_issue\":{\"max\":1},\"create_pull_request\":{\"base_branch\":\"${{ github.ref_name }}\",\"draft\":true,\"max\":1,\"max_patch_size\":1024},\"missing_data\":{},\"missing_tool\":{},\"noop\":{}}"

[Copilot]

The noop configuration has been removed from the GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG in this workflow. However, the workflow now includes an instruction for agents to call the "noop" tool (line 527): "Note: If you made no other safe output tool calls during this workflow execution, call the 'noop' tool to provide a status message indicating completion or that no actions were needed."

This creates an inconsistency: the workflow instructs users to call the "noop" tool, but the safe outputs handler configuration no longer includes the noop handler (line 1089). This means if the agent follows the instruction and calls the noop tool, it may not be processed correctly.

Either the noop configuration should be restored, or the instruction about calling the noop tool should be removed to maintain consistency.

[Copilot]

The noop configuration has been removed from the GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG in this workflow. However, the workflow now includes an instruction for agents to call the "noop" tool (line 570): "Note: If you made no other safe output tool calls during this workflow execution, call the 'noop' tool to provide a status message indicating completion or that no actions were needed."

This creates an inconsistency: the workflow instructs users to call the "noop" tool, but the safe outputs handler configuration no longer includes the noop handler (line 1144). This means if the agent follows the instruction and calls the noop tool, it may not be processed correctly.

Either the noop configuration should be restored, or the instruction about calling the noop tool should be removed to maintain consistency.

Suggested change

	GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":1},\"create_issue\":{\"close_older_issues\":true,\"max\":1,\"title_prefix\":\"${{ github.workflow }}\"},\"missing_data\":{},\"missing_tool\":{}}"
	GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":1},\"create_issue\":{\"close_older_issues\":true,\"max\":1,\"title_prefix\":\"${{ github.workflow }}\"},\"missing_data\":{},\"missing_tool\":{},\"noop\":{}}"

[Copilot]

The noop configuration has been removed from the GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG in this workflow. However, the workflow now includes an instruction for agents to call the "noop" tool (line 500): "Note: If you made no other safe output tool calls during this workflow execution, call the 'noop' tool to provide a status message indicating completion or that no actions were needed."

This creates an inconsistency: the workflow instructs users to call the "noop" tool, but the safe outputs handler configuration no longer includes the noop handler (line 1087). This means if the agent follows the instruction and calls the noop tool, it may not be processed correctly.

Either the noop configuration should be restored, or the instruction about calling the noop tool should be removed to maintain consistency.

Suggested change

	GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"create_pull_request\":{\"base_branch\":\"${{ github.ref_name }}\",\"draft\":true,\"max\":1,\"max_patch_size\":1024},\"missing_data\":{},\"missing_tool\":{}}"
	GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"create_pull_request\":{\"base_branch\":\"${{ github.ref_name }}\",\"draft\":true,\"max\":1,\"max_patch_size\":1024},\"missing_data\":{},\"missing_tool\":{},\"noop\":{}}"

[Copilot]

The noop configuration has been removed from the GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG in this workflow. However, the workflow now includes an instruction for agents to call the "noop" tool (line 651): "Note: If you made no other safe output tool calls during this workflow execution, call the 'noop' tool to provide a status message indicating completion or that no actions were needed."

This creates an inconsistency: the workflow instructs users to call the "noop" tool, but the safe outputs handler configuration no longer includes the noop handler (line 1275). This means if the agent follows the instruction and calls the noop tool, it may not be processed correctly.

Either the noop configuration should be restored, or the instruction about calling the noop tool should be removed to maintain consistency.

Suggested change

	GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":1},\"create_issue\":{\"max\":1,\"title_prefix\":\"${{ github.workflow }}\"},\"missing_data\":{},\"missing_tool\":{},\"push_to_pull_request_branch\":{\"base_branch\":\"${{ github.ref_name }}\",\"if_no_changes\":\"warn\",\"max_patch_size\":1024}}"
	GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":1},\"create_issue\":{\"max\":1,\"title_prefix\":\"${{ github.workflow }}\"},\"missing_data\":{},\"missing_tool\":{},\"noop\":{},\"push_to_pull_request_branch\":{\"base_branch\":\"${{ github.ref_name }}\",\"if_no_changes\":\"warn\",\"max_patch_size\":1024}}"

[Copilot]

The noop configuration has been removed from the GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG in this workflow. However, the workflow now includes an instruction for agents to call the "noop" tool (line 658): "Note: If you made no other safe output tool calls during this workflow execution, call the 'noop' tool to provide a status message indicating completion or that no actions were needed."

This creates an inconsistency: the workflow instructs users to call the "noop" tool, but the safe outputs handler configuration no longer includes the noop handler (line 1231). This means if the agent follows the instruction and calls the noop tool, it may not be processed correctly.

Either the noop configuration should be restored, or the instruction about calling the noop tool should be removed to maintain consistency.

Suggested change

GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":5,\"target\":\"*\"},\"create_discussion\":{\"category\":\"agentic-workflows\",\"close_older_discussions\":true,\"expires\":168,\"max\":5,\"title_prefix\":\"${{ github.workflow }}\"},\"create_issue\":{\"max\":3},\"create_pull_request\":{\"base_branch\":\"${{ github.ref_name }}\",\"draft\":true,\"max\":1,\"max_patch_size\":1024,\"title_prefix\":\"[qa] \"},\"missing_data\":{},\"missing_tool\":{}}"

GH_AW_SAFE_OUTPUTS_HANDLER_CONFIG: "{\"add_comment\":{\"max\":5,\"target\":\"*\"},\"create_discussion\":{\"category\":\"agentic-workflows\",\"close_older_discussions\":true,\"expires\":168,\"max\":5,\"title_prefix\":\"${{ github.workflow }}\"},\"create_issue\":{\"max\":3},\"create_pull_request\":{\"base_branch\":\"${{ github.ref_name }}\",\"draft\":true,\"max\":1,\"max_patch_size\":1024,\"title_prefix\":\"[qa] \"},\"missing_data\":{},\"missing_tool\":{},\"noop\":{}}"