Skip to content

SDK: Release selection, pagination and Plugin catalogue bindings #2719

Description

@gokhanarkan

Tracking consolidated

Remaining in-scope work is tracked in Data pipeline: catalogue, authentication and SDK, one of the four direct workstreams in epic #1230.

Closed as not planned for this separate tracker, not as implemented or delivered. This removes duplicate/nested tracking; the remaining requirements move to the workstream checklist. Plugin and Canvas resources are deferred; their consumer delivery is not a prerequisite for the current Skill/MCP releases. Existing history and implementation evidence are preserved below.

Previous scope and evidence

Parent: https://github.com/github/copilot-ecosystem/issues/1411
Epic: https://github.com/github/copilot-ecosystem/issues/1230

Outcome

Publish generated SDK transport for the newly merged runtime catalogue contracts and record the exact supported CLI/SDK versions for App and VS Code consumers.

Delivered runtime dependencies

  • Exact selection: github/copilot-agent-runtime#18529.
  • Pagination: github/copilot-agent-runtime#19902.
  • Typed Plugin candidates and compatibility metadata: github/copilot-agent-runtime#18555.
  • Preserve existing trust support from github/copilot-agent-runtime#18535.

Acceptance criteria

  • Verify actual canonical CLI Release archive source and schema contain the required merged contracts; a version/date alone is not proof.
  • Use the existing Update Copilot CLI Version action and checksum-verified GitHub Release assets. Reuse an appropriate existing update PR/run rather than duplicate it.
  • Generate and validate all supported SDKs without handwritten transport or broad decoder-policy changes.
  • Preserve the five legacy grants plus explicitly requested supported additions and typed refusal compatibility.
  • Record package-level smoke evidence for selection, page navigation and handleless Plugin candidates on the exact published versions; do not claim installation from discovery.
  • Publish through the normal reviewed SDK release flow and document minimum runtime/SDK versions plus client capability negotiation.
  • Provide the version handoff for App pins and VS Code adoption.

Scope separation

Closed #2106 delivered the earlier typed search baseline. #2389 retains its original stable search/planning binding evidence requirements; do not add these newer contracts to that older issue's closure bar. Existing #2703 targets CLI 1.0.86-2, which was verified to predate Plugin and pagination. Recheck any newer release's actual payload.

Executable planning/apply delivery follows its own runtime implementation and installation lane; unmerged future operations are not a prerequisite to this discovery-contract release. No SDK-owned networking, planning, downloading or installation is introduced.

Post-demo update: 18 September 2026

Release gate and priority separation

As of the 18 September verified payload read, CLI 1.0.86 and 1.0.86-2 package runtime 615005b5795ebea28929abdc43e4ad6acff6024f, which contains trust but predates selection/pagination/Plugin. Verify a newer canonical archive's actual schema/source before dispatch; an existing update PR or publication date does not satisfy this issue.

Existing #2703 targets the older 1.0.86-2 and the 1.0.86 updater failed codegen. Reuse/resolve the appropriate official update path without duplicate runs.

Future confirmed MCP/Skill installation publication is #2720; it does not become a new prerequisite for this discovery-contract release. Keep #2389's earlier evidence bar separate. Runtime/CLI development may proceed independently of public package publication; App requires the relevant supported version handoff.

Activity

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions