Skip to content

SDK: Promote catalogue search and planning APIs to stable #2389

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. Existing history and implementation evidence are preserved below.

Previous scope and evidence

Summary

Promote the generated catalogue search and planning surface from preview to a stable Copilot SDK release using an exact schema-bearing CLI package.

Parent: https://github.com/github/copilot-ecosystem/issues/1233
Related completed baseline: #2106
Epic: https://github.com/github/copilot-ecosystem/issues/1230

Current state

Stable SDK 1.0.14 now includes generated catalog.search and mcp.planInstall types and pins CLI 1.0.85. Stable packaging is delivered; the remaining work here is the original catalogue-specific acceptance evidence, not a claim that the bindings are broken. Executable planning and apply remain distinct runtime delivery stages.

Acceptance criteria

  • Code generation consumes an exact verified CLI/platform package version.
  • Node, Python, Go, .NET, Rust, and Java compile with the generated unions.
  • searchId, capabilities, handles, and typed authentication failures round-trip without message matching.
  • Search/plan separation and host confirmation requirements are documented.
  • No convenience plan-and-apply wrapper is introduced.
  • Stable release and artefact smoke results are recorded; apply remains explicitly unavailable until regenerated later.

Delivery status (18 September 2026)

  • Stable release v1.0.14, exact tagged source e60d9037353249ef16b349eb4012e8c1d113fda5, CLI pin 1.0.85; generated Node search/plan methods are present.
  • Existing six-language build/test run 35056790466 for merged release PR Complete Fast Auto-tier support across SDKs #2669, plus tagged-merge Codegen Check 35058385706.
  • Publication run 35058443716: package jobs succeeded; the overall red result was the Java documentation-site trigger, not a package-publishing failure.
  • Record stable-artefact semantic round trips preserving searchId, required/granted capabilities, candidate/plan handles and typed authentication failures without message matching.
  • Record a catalogue-specific smoke result using the exact stable SDK and verified CLI artefacts. Archive-layout/source tests alone do not establish this.
  • Cite shipped guidance for search/planning separation, explicit host confirmation and unavailable apply.

Accepted Java #2532 and normal compilation are credited, but do not by themselves prove all semantic requirements. Do not count abandoned #2486 code or tighten global SDK decoder behaviour to manufacture evidence.

Keep this issue open until the remaining original acceptance proof is recorded. Later selection/pagination/Plugin release work is separate: #2719; it is not added to this issue's closure bar.

Activity

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions