microsoft / microsoft/GitHub-Copilot-for-Azure
[Epic] Ship plugins through one predictable multi-client distribution path
@JasonYeMSFT is already working on this.
Since Jul 20, 2026.
- Dominant language
- Python
- Stars
- 250
- Forks
- 204
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 67
Description
## Problem statement
Plugin release, marketplace publication, synchronization, versioning, installation, and launch reviews currently span separate paths and repositories.
## Outcome
Plugins ship through one predictable multi-client distribution path with consistent versioning, review gates, installation, and update behavior.
## Goals
- Configure and maintain the multi-plugin marketplace
- Synchronize and stamp changed plugins predictably
- Validate installation and update behavior
- Complete Agency security, privacy, Responsible AI, legal, accessibility, and release-readiness gates
## Success criteria
- [ ] Marketplace publication and synchronization are automated and observable
- [ ] Versioning is correct for each changed plugin
- [ ] Install and update paths are validated
- [ ] Required Agency launch reviews are complete
## Tracked work
Release and marketplace: #2790, #2791, #2792, #2793
Agency launch gates: microsoft/GitHub-Copilot-for-Azure-pr#342 through microsoft/GitHub-Copilot-for-Azure-pr#348
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.