Update @github/copilot to 1.0.69-2

[github-actions]

Automated update of @github/copilot to version 1.0.69-2.

Changes

• Updated @github/copilot in nodejs/package.json and test/harness/package.json
• Re-ran all code generators (scripts/codegen)
• Formatted generated output
• Updated Java codegen dependency, POM property, and regenerated Java types

Java Handwritten Code Adaptation Plan

If java-sdk-tests CI fails on this PR, follow these steps:

1. Identify failures: Run mvn clean, mvn verify from java/ locally or check the java-sdk-tests workflow run logs.
2. Categorize errors:
   • Constructor signature changes (new fields added to generated records)
   • Enum value additions/renames in generated types
   • New event types requiring handler registration
   • Removed or renamed generated types
3. Fix handwritten source (java/src/main/java/com/github/copilot/sdk/):
   • Update call sites passing positional constructor args to include new fields (typically null for optional new fields).
   • Update switch/if-else over enum values to handle new cases.
   • Register handlers for new event types in CopilotSession.java if applicable.
4. Fix handwritten tests (java/src/test/java/com/github/copilot/sdk/):
   • Same constructor/enum fixes as above.
   • Add new test methods for new functionality if the change adds user-facing API surface.
5. Validate: cd java && mvn clean test-compile jar:jar && mvn verify -Dskip.test.harness=true
6. Format: cd java && mvn spotless:apply
7. Push fixes to this PR branch.

To automate this, trigger the java-adapt-handwritten-code-to-accept-upgrade-changes agentic workflow instead.

Next steps

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

Created by the Update @github/copilot Dependency workflow.

[stephentoub]

@SteveSandersonMS in #1901 how did you pull in 1.0.69-2? I was curious whether running the action would be a nop now, but it's not completely.

[github-actions]

Cross-SDK Consistency Review ✅

This PR updates @github/copilot from 1.0.69-1 to 1.0.69-2 and regenerates lock files. No SDK source files were modified (nodejs/src/, python/copilot/, go/, dotnet/src/, java/src/main/java/, rust/src/).

No cross-SDK consistency issues found. This is a dependency version bump with no API surface changes.

Generated by SDK Consistency Review Agent for issue #1914 · sonnet46 462.8K · ◷

[Copilot]

Pull request overview

Updates the repository’s pinned Copilot CLI/schema dependency to @github/copilot@1.0.69-2 for the Node-based test harness and Java codegen tooling, refreshing the corresponding lockfiles so CI and local development consume the new CLI artifacts.

Changes:

• Bumped @github/copilot to ^1.0.69-2 in the test harness.
• Updated npm lockfiles to resolve @github/copilot and all platform-specific optional packages to 1.0.69-2.
• Refreshed lockfile metadata for Linux platform packages (notably the absence of libc qualifiers in the lock entries).

Show a summary per file

File	Description
test/harness/package.json	Bumps harness devDependency on @github/copilot to ^1.0.69-2.
test/harness/package-lock.json	Updates resolved @github/copilot tarball/integrity and platform optionalDependencies to 1.0.69-2.
nodejs/samples/package-lock.json	Updates sample lockfile dependency resolution to @github/copilot ^1.0.69-2.
nodejs/package-lock.json	Updates resolved @github/copilot tarball/integrity and platform optionalDependencies to 1.0.69-2 (lock entry metadata changes included).
java/scripts/codegen/package-lock.json	Updates Java codegen lockfile to resolve @github/copilot and platform optionalDependencies to 1.0.69-2.

Review details

Files not reviewed (4)

• java/scripts/codegen/package-lock.json: Generated file
• nodejs/package-lock.json: Generated file
• nodejs/samples/package-lock.json: Generated file
• test/harness/package-lock.json: Generated file

• Files reviewed: 1/5 changed files
• Comments generated: 0
• Review effort level: Low

[SteveSandersonMS]

@stephentoub I told the agent to do the update. Seems like there are two main things where this has differed:

1. There are two other package.json files to be updated (Node samples and test harness) - not that either would make a difference to the shipped packages
2. The version of the toolchain my agent ran must differ from the one the automation uses, hence all the "libc": ["musl"] changes

Looks like we can merge this PR to bring it into sync.