Skip to content

On branch edburns/1146-support-three-more-permission-kind-values — Fixes #1146: bump test harness CLI to support new permission protocol#1150

Open
edburns wants to merge 2 commits intogithub:mainfrom
edburns:edburns/1146-support-three-more-permission-kind-values
Open

On branch edburns/1146-support-three-more-permission-kind-values — Fixes #1146: bump test harness CLI to support new permission protocol#1150
edburns wants to merge 2 commits intogithub:mainfrom
edburns:edburns/1146-support-three-more-permission-kind-values

Conversation

@edburns
Copy link
Copy Markdown
Contributor

@edburns edburns commented Apr 27, 2026

Changes to be committed:
(use "git restore --staged ..." to unstage)
modified: .gitignore
new file: test/harness/cliCompatibility.test.ts
- New regression test validating the harness CLI supports the current SDK permission protocol (approve-once, reject, user-not-available) and per-session auth (auth.getStatus, gitHubToken).
modified: test/harness/package-lock.json
- Regenerated lockfile; resolves @github/copilot to 1.0.36.
modified: test/harness/package.json
- Bumped @github/copilot from ^1.0.32 to ^1.0.36-0 so the harness CLI accepts the new PermissionDecision wire values and session.auth.getStatus RPC method introduced in commit dd2dcbc.

All 5 failures are pre-existing flaky tests unrelated to this PR's changes (which only touch package.json, package-lock.json, and add cliCompatibility.test.ts). The last 5 runs on main for each workflow are all green.

Job Failed Test Root Cause
Node.js (macOS) test/client.test.ts > CopilotClient > forwards defaultAgent in session.resume request No authentication info available — auth race in test setup
Node.js (ubuntu) Same as above Same
Node.js (windows) Same as above Same
.NET (macOS) MultiClientTests.One_Client_Rejects_Permission_And_Both_See_The_Result Event ordering race — received ToolExecutionCompleteEvent before expected sequence
Go (ubuntu) TestSessionFs/should_write_workspace_metadata_via_sessionFs ReplayingCapiProxy not yet initialized — proxy/test init race

Evidence these are pre-existing:

  • The forwards defaultAgent in session.resume test also failed in the first CI run (before the lockfile fix), confirming it's not caused by the CLI version bump.
  • The last 5 .NET SDK Tests runs on main all passed (#1220, #1214, #1198, #1195, #1194).
  • The last 5 Go SDK Tests runs on main all passed similarly.
  • The initial run had widespread esbuild platform failures on Windows/Linux due to a lockfile regeneration issue; this was fixed in commit 52f187f and those platforms now pass for .NET and Go.

Requesting re-run of failed jobs.

edburns added 2 commits April 27, 2026 18:06
 github#1146: bump test harness CLI to support new permission protocol

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
	modified:   .gitignore
	new file:   test/harness/cliCompatibility.test.ts
	- New regression test validating the harness CLI supports the current SDK permission protocol (`approve-once`, `reject`, `user-not-available`) and per-session auth (`auth.getStatus`, `gitHubToken`).
	modified:   test/harness/package-lock.json
	- Regenerated lockfile; resolves `@github/copilot` to 1.0.36.
	modified:   test/harness/package.json
	- Bumped `@github/copilot` from `^1.0.32` to `^1.0.36-0` so the harness CLI accepts the new `PermissionDecision` wire values and `session.auth.getStatus` RPC method introduced in commit `dd2dcbc`.
@edburns edburns marked this pull request as ready for review April 27, 2026 22:33
@edburns edburns requested a review from a team as a code owner April 27, 2026 22:33
Copilot AI review requested due to automatic review settings April 27, 2026 22:33
@SteveSandersonMS
Copy link
Copy Markdown
Contributor

@edburns Did you definitely observe that this makes a difference to the existing E2E tests in this repo? In my understanding, the changes here won't have any effect, since the version of @github/copilot referenced in test/harness is only for extracting a TypeScript type and isn't consumed at runtime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants