GitHub Release Notes
Last updated: Mar 3, 2026
GitHub Products
All GitHub Release Notes (126)
- Mar 3, 2026
- Date parsed from source:Mar 3, 2026
- First seen by Releasebot:Mar 3, 2026
GitHub Code Quality enterprise policy
GitHub adds separate control for Code Quality in Advanced Security so you can enable Code Quality enterprise wide without turning on Code Security. A new dedicated repository level policy page makes managing Code Quality easier and clearer.
You can now manage GitHub Code Quality availability separately from Code Security in GitHub Advanced Security policies. This gives you more flexibility to make GitHub Code Quality available across your enterprise without unintentionally enabling Code Security.
This update includes the following changes:
The Advanced Security enterprise policy settings no longer mention the Code Quality feature.
A dedicated policy page is now available to manage GitHub Code Quality at the repository level, similar to the existing Advanced Security policy experience.
Learn more about using enterprise policies to control access to GitHub Code Quality in our Code Quality documentation.
The post GitHub Code Quality enterprise policy appeared first on The GitHub Blog.
Original source Report a problem - Mar 2, 2026
- Date parsed from source:Mar 2, 2026
- First seen by Releasebot:Mar 3, 2026
Upcoming deprecation of Gemini 3 Pro and GPT-5.1 models
GitHub Copilot announces the deprecation of Gemini 3 Pro and GPT-5.1 models with scheduled dates and migration paths. Administrators should enable alternatives in Copilot settings and verify policy readiness; users will see replacements in the model selector. No immediate removal action is required from users.
Upcoming deprecation of Gemini 3 Pro and GPT-5.1 models
We will deprecate the following models across all GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions):
Model
Deprecation date
Suggested alternative
Gemini 3 Pro
2026-03-26
Gemini 3.1 Pro
GPT-5.1
2026-04-01
GPT-5.3-Codex
GPT-5.1-Codex
2026-04-01
GPT-5.3-Codex
GPT-5.1-Codex-Mini
2026-04-01
GPT-5.3-Codex
GPT-5.1-Codex-Max
2026-04-01
GPT-5.3-Codex
The Gemini 3 Pro deprecation date is accelerated due to provider deprecation.
Please update your workflows and integrations to use supported models before these dates. Copilot Enterprise administrators may need to enable access to alternative models through their model policies in Copilot settings. As an administrator, you can verify availability by checking your individual Copilot settings and confirming that the policy is enabled for the specific model. Once enabled, you’ll see the model in the Copilot Chat model selector in VS Code and on github.com. No action is required to remove the models once they have been deprecated.
GitHub Enterprise customers with questions or concerns are encouraged to reach out to their account manager for further assistance.Share your feedback
Share your feedback
To learn more about the models available in Copilot, see our documentation on models and get started with Copilot today.
Join the GitHub Community to share your feedback.The post Upcoming deprecation of Gemini 3 Pro and GPT-5.1 models appeared first on The GitHub Blog.
Original source Report a problem All of your release notes in one feed
Join Releasebot and get updates from GitHub and hundreds of other software products.
- Mar 2, 2026
- Date parsed from source:Mar 2, 2026
- First seen by Releasebot:Mar 3, 2026
Network configuration changes for Copilot coding agent now in effect
Copilot coding agent now uses plan-based network routing with new hosts, effective Feb 27 and now in effect. Self-hosted runners affected. Traffic routes to api.business.githubcopilot.com, api.enterprise.githubcopilot.com, or api.individual.githubcopilot.com; drop api.githubcopilot.com from allowlists.
Network configuration changes for Copilot coding agent now in effect
On February 13, 2026 we announced changes to the required network configuration for Copilot coding agent, taking effect on February 27.
These changes only affect teams running Copilot coding agent on self-hosted runners or larger runners with Azure private networking.
These changes have now taken effect. Copilot will apply subscription-based network routing, connecting to a different host depending on the Copilot plan of the user who initiated the agent task:
- Copilot Business: api.business.githubcopilot.com
- Copilot Enterprise: api.enterprise.githubcopilot.com
- Copilot Pro and Pro+: api.individual.githubcopilot.com
If your network is still configured to allow connections to api.githubcopilot.com for Copilot coding agent, you can now drop this host from your allowlist.
The post Network configuration changes for Copilot coding agent now in effect appeared first on The GitHub Blog.
Original source Report a problem - Mar 2, 2026
- Date parsed from source:Mar 2, 2026
- First seen by Releasebot:Mar 3, 2026
Copilot metrics now includes plan mode
Copilot now includes plan mode telemetry in usage metrics, enabling enterprises to track adoption and engagement across JetBrains, Eclipse, Xcode, and VS Code Insiders. Plan mode data appears in totals by feature and in the dashboard under Insights > Copilot usage.
Copilot usage metrics now includes plan mode telemetry. Enterprises can track adoption and engagement trends for plan mode alongside existing Copilot metrics, enabling a more complete view of how teams are implementing plans directly in their IDE.
Availability
Plan mode telemetry is included as part of the broader Copilot usage metrics experience. Please ensure Copilot usage metrics is enabled for the enterprise or organization.
Telemetry is supported for JetBrains, Eclipse, Xcode, and VS Code Insiders at the enterprise, organization, and user-level. General release for VS Code is expected soon.
Within the API response, usage will be denoted by chat_panel_plan_mode under the keys totals_by_feature, totals_by_language_feature, and totals_by_model_feature.
Within the dashboard UI, view plan mode breakdowns for request and model usage under Insights > Copilot usage.
Important note
Telemetry for plan mode used to be mixed in with "Custom". Now that it's properly broken out, you may see a dip in "Custom" usage. This may affect dashboard charts like "Requests per chat mode" and "Model usage per chat mode".
Join the discussion within GitHub Community.
The post Copilot metrics now includes plan mode appeared first on The GitHub Blog.
Original source Report a problem - Mar 2, 2026
- Date parsed from source:Mar 2, 2026
- First seen by Releasebot:Mar 3, 2026
Copilot metrics reports now return consistent usernames for Enterprise Managed Users
GitHub Copilot usage metrics reports now return a consistent user_login value for Enterprise Managed Users (EMU)
GitHub Copilot usage metrics reports now return a consistent user_login value for Enterprise Managed Users (EMU). Previously, some reports could include a suffix in user_login, which made it harder to match results across GitHub APIs.
The post Copilot metrics reports now return consistent usernames for Enterprise Managed Users appeared first on The GitHub Blog.
Original source Report a problem - Mar 2, 2026
- Date parsed from source:Mar 2, 2026
- First seen by Releasebot:Mar 2, 2026
0.0.421-1
Improved
AUTO theme now reads your terminal's ANSI color palette and uses it directly, so colors match your terminal theme
Original source Report a problem - Mar 2, 2026
- Date parsed from source:Mar 2, 2026
- First seen by Releasebot:Mar 2, 2026
0.0.421-0
ACP clients gain session config for reasoning effort and repo-wide settings via config.json. Terminal UI improves Markdown tables and MCP forms, streaming output, and right-click paste. Windows shell output no longer garbles, and GitHub API errors aren’t shown as raw messages.
Added
- ACP clients can configure reasoning effort via session config options
- Click links in the terminal to open them in your default browser
- Support repo-level config via .github/copilot/config.json for shared project settings like marketplaces and launch messages
Improved
- Markdown tables render with proper column widths, word wrap, and Unicode borders that adapt to terminal width
- MCP elicitation form displays taller multi-line text input, hides tab bar for single-field forms, and fixes error flashing on field navigation
Fixed
- Streaming output no longer truncates when running in alt-screen mode
- Right-click paste no longer produces garbled text on Windows
- Shell command output on Windows no longer renders as "No changes detected" in the timeline
- GitHub API errors no longer appear as raw HTTP messages in the terminal when using the # reference picker
- Feb 27, 2026
- Date parsed from source:Feb 27, 2026
- First seen by Releasebot:Feb 28, 2026
Copilot usage metrics now includes enterprise-level GitHub Copilot CLI activity
GitHub Copilot expands enterprise metrics to include CLI telemetry, tracking active CLI users, requests, sessions, and token usage to reveal how developers work with Copilot across environments. This update helps plan rollout, spot enablement gaps, and optimize adoption.
Copilot enterprise usage metrics coverage has expanded to now include Copilot CLI telemetry
With this update, your enterprise metrics can include CLI-specific activity and usage totals, such as:
- Daily active CLI users
- CLI request and session counts
- Token usage totals, including average tokens per request
Why this matters
- Track CLI adoption across your enterprise and spot where enablement or support is needed.
- Compare usage patterns across environments so you can understand how developers use GitHub Copilot day to day.
- Use token usage totals to better understand consumption trends and plan for rollout over time.
Join the discussion within GitHub Community.
The post Copilot usage metrics now includes enterprise-level GitHub Copilot CLI activity appeared first on The GitHub Blog.
Original source Report a problem - Feb 27, 2026
- Date parsed from source:Feb 27, 2026
- First seen by Releasebot:Feb 28, 2026
Copilot metrics is now generally available
GitHub Copilot usage metrics is generally available with enterprise dashboards, APIs, and fine grained access controls to track adoption and usage across teams, now with data residency. This release moves from preview to full production availability and impact.
Copilot metrics is now generally available
GitHub Copilot usage metrics is now generally available, giving you a single place to see how your teams adopt and use Copilot. This way you can track trends, make informed decisions about rollout, and build reports that fit your organization.
Since the public preview at Universe 2025, Copilot usage metrics has expanded with organization-level visibility, fine-grained access controls, data residency support, and more. Here’s what you can expect now that it’s generally available.What’s included
- Dashboards
- Copilot usage dashboard provides clear, actionable insights into how your teams are using GitHub Copilot. The dashboard provides visibility into code completion activity, IDE usage, model and language breakdown, and more.
- Code generation dashboard gives a directional measure of Copilot’s output by quantifying the lines it suggested, added, or deleted across completions, chat, and agent features.
- Enterprise and organization-level granularity allows enterprise and organization owners to track adoption and usage trends for their teams without relying solely on enterprise-wide aggregates.
- APIs
- Enterprise-level: Get a bird’s eye view of all Copilot usage across your entire enterprise for aggregate analysis on user engagement, Copilot usage, pull request throughput, and more.
- Organization-level: Organizations can programmatically access their own Copilot usage to understand how teams are engaging with Copilot, spot trends, and assess enablement efforts.
- User-level: Analyze individual Copilot usage for a specific day to support enablement and identify where teams may need training or better documentation.
- Check out our API documentation to learn more.
Access and availability
- For access, navigate to your enterprise account → AI Controls → Copilot → Metrics → Copilot usage metrics. You should then see the dashboard under Insights → Copilot usage or Code generation. Please also ensure you are either an Enterprise Administrator, Billing Manager, or have the proper fine-grained permissions to have access to Copilot metrics.
- Fine-grained access controls let you share visibility with the right people using custom enterprise roles, such as View enterprise Copilot metrics, without requiring full admin access.
- Added support for GitHub Enterprise Cloud with data residency so enterprises with residency requirements can access Copilot usage dashboards and API reporting.
What’s next
Today’s release delivers the data foundation for understanding Copilot adoption across your organization. The next question many leaders are asking is “is it working?” We’re building toward that answer—connecting usage patterns to engineering outcomes so you can move from tracking adoption to measuring impact. We’ll share more as these capabilities become available.
Original source Report a problem
To get started, visit Copilot usage metrics documentation. Join the discussion within GitHub Community.
The post Copilot metrics is now generally available appeared first on The GitHub Blog. - Feb 27, 2026
- Date parsed from source:Feb 27, 2026
- First seen by Releasebot:Feb 28, 2026
0.0.420
2026-02-27
- Auto-update now also updates the binary executable, not just the JS package
- Plugin and marketplace git repos update correctly after force-pushes and tag-based installs
- 502 bad gateway errors are retried automatically and no longer crash the session with raw HTML output
- Copy hint shows cmd+c in Ghostty on macOS and right-click as an alternative for all terminals
- Type # to reference GitHub issues, pull requests and discussions