Update @github/copilot to 1.0.39#1167
Merged
stephentoub merged 2 commits intomainfrom Apr 29, 2026
Merged
Conversation
- Updated nodejs and test harness dependencies - Re-ran code generators - Formatted generated code
Contributor
There was a problem hiding this comment.
Pull request overview
Automated dependency bump of @github/copilot to 1.0.39 across the Node SDK and test harness, with regenerated multi-language session-event types to reflect updated schema fields.
Changes:
- Updated
@github/copilotversion from^1.0.39-0to^1.0.39in Node packages and refreshed lockfiles. - Regenerated session-event models/types to include new optional fields (
eligibleForAutoSwitch,errorCode,cause,retryAfterSeconds) across TS/Go/.NET/Python. - Updated the Node samples lockfile to reflect the new dependency graph via the local
file:..SDK link.
Show a summary per file
| File | Description |
|---|---|
| test/harness/package.json | Bumps @github/copilot devDependency to ^1.0.39. |
| test/harness/package-lock.json | Updates resolved @github/copilot (and platform optional deps) to 1.0.39. |
| nodejs/package.json | Bumps @github/copilot dependency to ^1.0.39. |
| nodejs/package-lock.json | Updates resolved @github/copilot (and platform optional deps) to 1.0.39. |
| nodejs/samples/package-lock.json | Updates the linked SDK’s resolved dependency graph to @github/copilot@^1.0.39. |
| nodejs/src/generated/session-events.ts | Adds new optional fields to generated session event data interfaces. |
| python/copilot/generated/session_events.py | Adds new optional fields and (de)serialization support in generated session event dataclasses. |
| go/generated_session_events.go | Adds new optional fields to generated Go session event structs. |
| dotnet/src/Generated/SessionEvents.cs | Adds new nullable properties to generated .NET session event DTOs. |
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
- Files reviewed: 3/9 changed files
- Comments generated: 0
Mirror the synchronization pattern from the 'approve' sibling: capture a PermissionCompletedEvent task on session2 before subscribing and sending, then await it before asserting that client2 observed PermissionRequestedEvent. Without this wait, client2's event subscription could be asserted before the event had propagated, causing intermittent failures (observed on macOS CI). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
Cross-SDK Consistency Review ✅This automated schema update (
No consistency issues found. The generated code follows each language's conventions (camelCase for TypeScript, snake_case for Python, PascalCase for Go exported fields and .NET properties).
|
tclem
added a commit
that referenced
this pull request
Apr 30, 2026
Closes "Mode 1 hands-off loop" gap A from the SDK release plan-doc: update-copilot-dependency.yml is workflow_dispatch only today, so when a new @github/copilot publishes nobody automatically opens the regen PR. Today's bot-driven bump (commit ecdc5ec, "Update @github/copilot to 1.0.39 (#1167)") was triggered manually after the plan-doc session noticed the gap. Goal: the SDK auto-detects new CLI versions, opens a draft PR with all per-language regen + formatting + lockfile updates, and a human just reviews + merges. github-app's bundled-binary tracker picks the new SDK up via crates.io dependabot in the symmetric direction. Changes: 1. **`schedule` trigger.** Daily cron at 10:00 UTC, deliberately symmetric with github-app's check-bundled-binary-versions.yml so the SDK and consumer halves of the loop tick in lockstep on release days. 2. **`version` input is now optional.** Manual override still works for emergency back-patches or cherry-picking specific prereleases; an empty input on workflow_dispatch flows through the same auto-detect path the schedule uses. 3. **Two-job split: `detect` -> `update`.** The detect job is cheap (one `npm view @github/copilot version` + a jq read of nodejs/package.json + a strip of the `^`/`~` prefix). It sets two outputs: - `version`: the resolved target (input override, or latest from npm) - `should_continue`: 'true' if the resolved version differs from the current pin, 'false' otherwise The update job has `needs: detect` and `if: needs.detect.outputs.should_continue == 'true'`, so it skips entirely when there's nothing to do. This keeps the no-op daily cost effectively free. 4. **Validation moves into the resolve step.** Both manual and auto-detected versions go through the same semver regex check. The previous standalone "Validate version input" step is retired; the detect job's resolve step now owns format validation, version comparison, and skip logic. 5. **All `${{ inputs.version }}` references become `${{ needs.detect.outputs.version }}`.** Same value, just routed through the detect job's outputs so manual override and auto-detect both feed the update job uniformly. Doesn't touch SDK source; cargo test / cargo publish --dry-run are no-op confirmation post-merge. Companion gap on the github-app side (auto-open sync PR after each new SDK release) lives on Sync session PR #4140; this commit unblocks the SDK half. Plan-doc capture: tracked under "Steady-state CLI bump automation (Mode 1 hands-off loop)" — gap A closed; gap B (github-app sync-PR auto-open) remains. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated update of
@github/copilotto version1.0.39.Changes
@github/copilotinnodejs/package.jsonandtest/harness/package.jsonscripts/codegen)Next steps
When ready, click Ready for review to trigger CI checks.