Update @github/copilot to 1.0.40-1

[github-actions]

Automated update of @github/copilot to version 1.0.40-1.

Changes

• Updated @github/copilot in nodejs/package.json and test/harness/package.json
• Re-ran all code generators (scripts/codegen)
• Formatted generated output

Next steps

When ready, click Ready for review to trigger CI checks.

Created by the Update @github/copilot Dependency workflow.

[Copilot]

Pull request overview

This PR updates the mono-repo’s Copilot CLI schema dependency (@github/copilot) to 1.0.40-1 and refreshes the generated RPC + session-event types across the Node, Python, Go, and .NET SDKs so the SDKs stay aligned with the updated protocol.

Changes:

• Bumped @github/copilot dependency versions in Node packages (SDK + test harness + samples lockfile).
• Regenerated RPC and session-event types across languages, picking up new/changed protocol fields (e.g., PermissionResult, expanded external tool results, new token metrics fields, new turnId fields).
• Reformatted generated output.

Show a summary per file

File	Description
test/harness/package.json	Bumps @github/copilot devDependency.
test/harness/package-lock.json	Lockfile refresh for updated Copilot package + platform artifacts.
nodejs/package.json	Bumps @github/copilot dependency.
nodejs/package-lock.json	Lockfile refresh for updated Copilot package + platform artifacts.
nodejs/samples/package-lock.json	Lockfile refresh for samples to match updated Copilot dependency.
nodejs/src/generated/rpc.ts	Regenerated Node RPC types (notably external tool result and permissions changes).
nodejs/src/generated/session-events.ts	Regenerated Node session-event types (notably PermissionResult, usage/token details, new IDs/flags).
python/copilot/generated/rpc.py	Regenerated Python RPC types (notably HandlePendingToolCall* request/result shape changes).
python/copilot/generated/session_events.py	Regenerated Python session-event types (PermissionResult, new metrics/fields).
go/rpc/generated_rpc.go	Regenerated Go RPC types (notably ExternalToolResult union + HandlePendingToolCall* changes).
go/generated_session_events.go	Regenerated Go session-event types (PermissionResult, new metrics/fields).
dotnet/src/Generated/Rpc.cs	Regenerated .NET RPC types (notably HandlePendingToolCall*, usage metrics details).
dotnet/src/Generated/SessionEvents.cs	Regenerated .NET session-event types (PermissionResult polymorphism, new metrics/fields).

Copilot's findings

Files not reviewed (3)

• nodejs/package-lock.json: Language not supported
• nodejs/samples/package-lock.json: Language not supported
• test/harness/package-lock.json: Language not supported

Comments suppressed due to low confidence (1)

go/rpc/generated_rpc.go:3393

• ToolsApi.HandlePendingToolCall puts *params.Result into the request map. ExternalToolResult is a union type (string | object), but in Go it’s represented as a struct with pointer fields; without a custom marshaler this will serialize as an object with String/ExternalToolTextResultForLlm fields instead of the union value the RPC expects. Fix by either (a) adding MarshalJSON/UnmarshalJSON for ExternalToolResult (similar to the existing union helper), or (b) setting req["result"] to the underlying string/object variant rather than the wrapper struct.

	if params != nil {
		req["requestId"] = params.RequestID
		if params.Result != nil {
			req["result"] = *params.Result
		}

• Files reviewed: 4/13 changed files
• Comments generated: 2

[github-actions]

Cross-SDK Consistency Review ✅

This PR (automated update to @github/copilot 1.0.40-1) maintains strong cross-SDK consistency. Here's a summary of findings:

New public API: continuePendingWork / ContinuePendingWork / continue_pending_work

The new option is added to ResumeSessionConfig across all four SDKs with appropriate language-idiomatic naming:

SDK	Config field	Function parameter
Node.js	continuePendingWork?: boolean	same (inline)
Python	continue_pending_work: bool (TypedDict, total=False)	continue_pending_work: bool | None = None
Go	ContinuePendingWork bool	— (struct field)
.NET	ContinuePendingWork: bool?	— (property)

All SDKs default to false / null / nil (i.e., pending work is not continued unless explicitly requested), which is consistent.

Generated code (schema-driven)

All generated files (rpc.ts, session-events.ts, generated_rpc.go, generated_session_events.go, Rpc.cs, SessionEvents.cs, rpc.py, session_events.py) are updated by codegen and consistently include:

• continuePendingWork and sessionWasActive in SessionResumeData
• turnId in AssistantMessageData, ToolExecutionStartData, ToolExecutionCompleteData
• New PermissionDecisionApprovePermanently variant
• tokenDetails / totalNanoAiu in usage metrics types
• Rename: ToolsHandlePendingToolCallRequest → HandlePendingToolCallRequest, ToolCallResult → ExternalToolTextResultForLlm (internal types)

Tests

Unit tests covering continuePendingWork payload forwarding exist in Node.js (client.test.ts), Go (client_test.go), and .NET (CloneTests.cs). Python does not have a dedicated unit test for continue_pending_work forwarding, though the implementation follows the same pattern as other parameters in the Python SDK.

No cross-SDK consistency issues found.

Generated by SDK Consistency Review Agent for issue #1177 · ● 363.1K · ◷