AWS says Copilot CLI will reach end of support June 12, 2026. If you’ve standardized on Copilot’s manifests and workflows, now is the moment to choose a migration path that preserves your deployment ergonomics while improving infra visibility.
GitHub says Copilot code review is now generally available on an agentic, tool-calling architecture that can pull broader repository context on demand — and it runs on GitHub Actions. That combination shifts cost, governance, and security considerations for engineering orgs. Here’s how to evaluate it, especially if you use self-hosted runners.
GitHub is deprecating several Copilot models (including GPT-5.1) and changing required network routing for Copilot coding agent. If you run agents on self-hosted runners, your allowlists and model policies need attention now.
GitHub is rolling Copilot usage metrics down from enterprise to organization scope, enabling least-privilege reporting. For platform and security teams, this is the missing layer for governing AI coding tools without centralizing all visibility at the enterprise tier.
GitHub is previewing an organization-level Copilot usage metrics dashboard. For platform engineering, it’s a sign that AI tooling will be governed like any other shared service: measured, costed, and optimized. Here’s what to track and how to operationalize it.
GitHub is expanding Copilot coding agent to better support Windows projects and code referencing. This is a platform engineering moment: autonomous agents are becoming a first-class CI actor, and repos will need new guardrails.
