[go: up one dir, main page]
Changelog

Subscribe to all Changelog posts via RSS or follow GitHub Changelog on Twitter to stay updated on everything we ship.

→ ~ cd github-changelog
→ ~/github-changelog|main git log main
showing all changes successfully

OpenAI GPT-4.5 in GitHub Copilot now available in public preview

GitHub Copilot GPT-4.5

OpenAI’s latest model, GPT-4.5, is now available in GitHub Copilot Chat to Copilot Enterprise users. GPT-4.5 is a large language model designed with advanced capabilities in intuition, writing style, and broad knowledge. It performs effectively with creative prompts and provides reliable responses to obscure knowledge queries. GPT-4.5 will launch in Visual Studio Code and on github.com for Copilot Enterprise users with a limit of 10 requests every 12 hours per user. In the coming weeks, we’ll be scaling rate limits and extending support to Visual Studio and JetBrains.

GPT 4.5 in the VS Code Model Picker

As model releases have continued to accelerate, we’ve been thinking about how we can sustainably offer advanced AI models like GPT-4.5 to more GitHub users. This includes individual developers who want the most advanced capabilities from day one. Stay tuned for updates.

Enabling access

Copilot Enterprise administrators will need to enable access to GPT-4.5 via a new policy in Copilot settings. As an administrator, you can confirm availability by checking your individual Copilot settings and confirming the policy for GPT-4.5 is set to “enabled”. Once enabled, users will see GPT-4.5 in the Copilot Chat model selector in VS Code and on github.com.

See more

Scheduled Codespaces maintenance

Codespaces will be undergoing maintenance in Europe and Southeast Asia from 17:00 UTC on Friday, February 28 to 02:00 UTC on Saturday, March 1. Maintenance will begin in North Europe at 17:00 UTC on Friday, February 28. Once it is complete, maintenance will start in Southeast Asia, followed by UK South. Each region will take approximately two to three hours to complete.

During this time period, users may experience connectivity issues with new and existing Codespaces.

If you have uncommitted changes you may need during the maintenance window, you should verify they are committed and pushed before maintenance starts. Codespaces with any uncommitted changes will be accessible as usual once maintenance is complete.

See more

Changes and deprecation notice for npm replication APIs

We are making changes to npm replication APIs to optimize performance and availability. As part of this update, certain endpoints will be deprecated as of Thursday, May 29, 2025.

To facilitate a seamless transition, the new endpoints will be available starting Tuesday, March 18, 2025, operating in parallel with the existing endpoints. The existing endpoints will be fully deprecated on Thursday, May 29, 2025.

During the transition period, you may access the new endpoints by including the npm-replication-opt-in header with the value true in your requests. This option will be available from Tuesday, March 18, 2025 until the deprecation date, after which only the new endpoints will be available. Effective Thursday, May 29, 2025, the header will be ignored, and all requests will be directed to the new endpoints by default.

This notice is provided to ensure adequate time for necessary updates to replication implementations. We strongly encourage developers to migrate to the new endpoints as early as possible.

How to migrate?

To assist with migration, we have detailed documentation in our replication API migration community discussion, outlining alternative approaches for deprecated endpoints when available. This is the go-to place for questions and discussions.

Additional support for migration

If you have further questions or need additional assistance, please reach out to our support team.

See more

Manage push protection bypass requests for secret scanning with the REST API

Push protection for secret scanning blocks any push that contains a secret. By default, this block can be bypassed, which results in a secret scanning alert in the repository. Delegated bypass controls let you choose who is allowed to bypass push protection, and contributors without permissions to bypass must submit a request for approval by the listed reviewers. These controls can reduce the risk of secrets being accidentally exposed in your codebase.

Managing bypass requests is now available with the REST API, offering flexibility for triaging and reviewing by integrating with your existing workflows.

Reviewers can retrieve bypass requests for an organization or repository with the following endpoints:

Reviewers can review a request and dismiss a response to a request with the following endpoints:

Learn more about how to secure your repositories with secret scanning and push protection.

See more

It is easier to track your progress with fixed code scanning CodeQL security alerts on the Security Overview page

Now it is easier to see how many of your historical CodeQL alerts received autofix suggestions and how many of those alerts were resolved across all the repositories in your organization.

Historical alerts are those found in your default and protected branches, indicating potential existing security issues in your code. You can stay informed about the progress of historical alert resolution and expediting this process as it is essential for accurately assessing your security risks.

Screenshot of total alerts fixed with an accepted autofix out of all with a suggested autofix.

The new “Alerts fixed with autofix suggestions” tile on the Security Overview provides you with the total number of fixed vulnerabilities compared to the total suggested autofixes for existing alerts. This will help you stay informed about the security trends in your organization.

Learn more about Copilot Autofix for CodeQL code scanning and security overview.

To leave feedback for Copilot Autofix for code scanning, join the discussion.

See more

Phi-4-mini-instruct and Phi-4-multimodal-instruct are now available in GitHub Models (GA)

Phi-4-mini-instruct and Phi-4-multimodal-instruct models release
The latest AI models from Phi, 4-mini-instruct and 4-multimodal-instruct, are now available in GitHub Models.

Phi-4-mini-instruct is a 3.8B parameter lightweight model designed for chat-completion prompts and strong reasoning, particularly in math and logic. Its efficiency makes it well-suited for memory- and compute-constrained environments.

Phi-4-multimodal-instruct is a 5.6B parameter multimodal model that excels at generating text outputs from various inputs including text, images, and audio. This model demonstrates strength in reasoning across multiple modalities.

GitHub Models makes it easy for every developer to build AI features and products on GitHub.

Try, compare, and implement these models in your code for free in the playground (Phi-4-mini-instruct and Phi-4-multimodal-instruct) or via the API.

To learn more about GitHub Models, check out the docs. You can also join our community discussions.

See more

Increased items in GitHub Projects now in public preview

Following our opt-in preview last October, we’re excited to expand item limits for all projects — increasing from 1,200 to 50,000 items per project.

Since the last release, we’ve added support for project insights and mobile, addressed your top bug reports, and delivered key performance improvements.

We’re rolling out increased limits incrementally over the next week. If you see the Increased items preview pill in your project, you’re now in the preview.

Insights for all

With this release, we’re also making project insights fully accessible to all plans—removing paid gating entirely. All plans now have access to both current state and historical charts in public and private repositories, with no feature restrictions. Learn more about insights for projects.

For questions and feedback, join the discussion within the GitHub Community.

See more

Copilot secret scanning can be enabled through code security configurations

Copilot secret scanning, which scans for passwords using AI, offers greater precision for detecting unstructured credentials that can cause security breaches if exposed.

You can now use code security configurations to enable Copilot secret scanning across your enterprise or organization, allowing you to control which repositories are detecting passwords at scale.

Copilot secret scanning is available for all repositories with a GitHub Advanced Security license. You do not need a Copilot license. To give you control over how AI is used across your repositories, Copilot secret scanning is not included in the GitHub Recommended configuration.

Learn more about protecting your repositories with secret scanning and generic secret detection.

See more

Code review in GitHub Copilot is now in public preview

Copilot Code Review

No more wait: Copilot code review is here

Code review is one of the most critical parts of software development. Manual code reviews, while essential, can be time-consuming. Copilot code review helps you offload basic reviews to a Copilot agent that finds bugs, potential performance problems, and even suggests automatic fixes. This means you can start iterating on your code while you wait for a human review—helping you keep your code repositories more maintainable and focused on quality.

Today we’re excited to announce that all Copilot subscribers can now use Copilot code review, with a host of updates that we’ve made since its initial preview. To get started, sign up here.

What’s new

  • Review summary: Copilot gives you a detailed summary of the changes in a pull request—bridging the gap between automated feedback and human insight.
  • Smarter reviews: We’re leveraging the latest models to provide even more insightful and effective feedback, identifying potential issues you might otherwise miss.

Here’s Copilot code review in action, providing a summary of the pull request and some suggested improvements:

To request a code review from Copilot, you can set up automatic reviews in a repo through repository rules. Or, if you prefer, you can ask Copilot to review a pull request on demand.

You can also jump directly into the new Copilot Workspace experience from your pull request, to refine and validate Copilot’s suggestions. And don’t forget, you can always review your code in Visual Studio Code before you push it to GitHub, keeping your development process agile and efficient.

To learn more, check out the docs. We can’t wait for you to try out these improvements, and we’d love your feedback in this GitHub Community Discussion.

See more

GitHub Copilot now available for free in Windows Terminal Canary

GitHub Copilot now available for free in Windows Terminal Canary

GitHub Copilot on Windows Terminal Canary is now available for free! GitHub Copilot Free allows you to access 50 chat messages per month. If you reach your quota, you can upgrade on the web.

GitHub Copilot in Windows Terminal

You can access the power of GitHub Copilot to get command suggestions and explanations without leaving the terminal with Terminal Chat in Windows Terminal Canary. This is available for all Copilot customers.

Get started today

GitHub Copilot is available in Windows Terminal Canary. Consult the Terminal Chat documentation to learn how to connect Copilot and get started.

Share your feedback

We are dedicated to continuous improvement and innovation. Your feedback remains a crucial part of our development process.
Learn more about GitHub Copilot Free and share your feedback on Terminal Chat.

See more

Enhanced billing platform is now available for personal accounts

As of February 13, 2025, new GitHub Free and Pro plan customers now have access to the enhanced billing platform—a suite of features designed to help users manage and understand their GitHub spending. All new users, regardless of plan type, are onboarded to this new experience.

Benefits of the new platform include:

  • Spend transparency: view usage for repositories, products, and SKUs by day, month, or year
  • Improved control: set budgets to limit spending and configure alerts to stay informed of budget utilization

Image

What to expect

Existing users on personal accounts will gain access to the enhanced billing platform in the coming months. You will be informed via email and an in-app banner on the billing page in advance of the transition.

Here are some things to know about the transition:

  • Once transitioned, a new Billing & Licensing section will appear in the enterprise account menu.
  • Spending limits will be migrated and renamed as budgets in the new billing platform. For more details about budgets, visit Preventing overspending.
  • While the new billing platform will not visually display historical usage, you will be able to download a usage report to get your pre-transition historical usage.

Other important changes

  • Git Large File Storage will transition from prepaid, quota-based data packs to a usage-based metered billing model. If you use Git Large File Storage today, you’ll receive credits for any unused data packs. For more information, visit “About enhanced billing for Git Large File Storage.”

Learn more

For more information, visit Using the enhanced billing platform for organizations.

See more

Repositories – Updated insight views (General Availability)

We’ve updated the contributors and code frequency repository insight views to improve navigation, allow hiding a series by interacting with the chart legend, and enable viewing and downloading the data as a CSV or PNG.

Contributors

Screenshot of new contributors chart showing github/explore

  • Keyboard-navigable date range selector: You can select date ranges using either your mouse or keyboard for improved accessibility. The available date ranges remain weekly (Sunday to Sunday), and we will only display contributors active within the selected timeframe.
  • Shareable URLs for specific views: The URL now reflects the selected time period, making it easy to share or bookmark a particular view.

Code frequency

Screenshot of new code frequency chart showing github/explore

  • The two axes are now differentiated by line style as well as color.
  • Data points are navigable and show more detail in a tooltip. Previously, you could only reference the axes visually.

Join the discussion in GitHub Community.

See more

GitHub Enterprise Server 3.16 release candidate is now available

GitHub Enterprise Server 3.16 enhances deployment efficiency, monitoring capabilities, code security, and policy management. Here are a few highlights in the 3.16 release:

  • The reliability, observability, and efficiency of ghe-config-apply have been improved. As a result, you may experience reduced downtime when ghe-config-apply is run.

  • The monitor dashboard has been optimized with concise, actionable metrics, providing a quick overview of the appliance’s operational health. For more details, see the monitor dashboard.

  • When reviewing code security configurations, you can now filter repositories more easily with new options that sort by the status of specific GHAS features. For more details, see new advanced filters for code security configurations.

  • You can now apply code security configurations to archived repositories, simplifying rollouts and ensuring features like Dependabot, code scanning, and secret scanning are automatically reapplied if a repository is unarchived. Additionally, you can now create and manage code security settings at the enterprise level, reducing repetitive setup at the organization level. For more details, see enterprise-level code security configurations.

  • Monitor prevention metrics alongside detection and remediation metrics for Dependabot and GitHub Advanced Security features, including secret scanning and code scanning. This expanded visibility is now available in the enhanced security overview dashboard at both organization and enterprise levels. For more information, see enhanced security overview dashboard.

  • Organization owners can now allow their users to set custom properties during repository creation. This ensures appropriate rules are enforced from the moment of creation and improves discoverability of new repositories. For more information, see custom properties.

  • Organization owners can now configure policies to restrict the usage of deploy keys across all the repositories of your organizations, giving you more control and greater security over your deploy keys. For more information, see enforcing a policy for deploy keys.

Release candidates are a way for you to try the latest features early, and they help us gather feedback to ensure the release works in your environment. They should be tested on non-production environments. Read more about the release candidate process.

To learn more about GHES 3.16, check out release notes, or download the 3.16 release candidate now.

If you have any feedback or questions about the release candidate, please contact our support team.

See more

Refining messages and reloading responses in Copilot Chat is now in public preview

A stylized image showing a 3D Copilot head looking at a user message that has been edited via the new editing functionality

The immersive mode of Copilot chat on GitHub now provides you with increased control and flexibility at every step.

What’s new:

  • ✏️ Edit your previously sent messages: Refine your messages whenever you need
  • 🔄 Reload responses: Get different variations instantly
  • 📝 Keep track of all iterations in one place: Easily view the history of your message edits and responses
  • 🔍 Compare different message and response pairs seamlessly: Switch between versions to see which one works best

Pro tips:

  • 🛠️ Fix typos or add context without starting over
  • 🧪 Experiment with different phrasings to get the best responses
  • 🔀 Toggle between versions to compare outcomes

These new refining capabilities make it easier to iterate with Copilot. Make adjustments and improvements while maintaining the full context of your conversations, helping you to stay focused when chatting with Copilot chat.

We hope these changes help keep you in the flow state when chatting with Copilot on GitHub.com 💫.

💬 Let us know what you think using the in-product feedback option or pop it into the GitHub Community at any time.

See more

Dependabot version updates now support Docker Compose in general availability

Developers can now use Dependabot to keep their Docker Compose dependencies up to date automatically. For projects that use Docker Compose as a package manager, Dependabot version updates can now ensure dependencies stay current with the latest releases.

See more

Claude 3.7 Sonnet is now available in GitHub Copilot in public preview

Claude 3.7 Sonnet is now available to all customers on paid Copilot plans. This new Sonnet model supports both thinking and non-thinking modes in Copilot. In initial testing, we’ve seen particularly strong improvements in agentic scenarios.

In GitHub’s internal evals, the model shows improvements over its predecessor in the ability to follow instructions, break down complex tasks, and build new UIs (human-reviewed).

Get started today!

Copilot Pro users

You can start using the new Claude 3.7 Sonnet model today via the model selector in Copilot in Visual Studio Code, Visual Studio, JetBrains IDEs, and immersive chat on GitHub.com.

Copilot Business or Enterprise users

Copilot Business and Enterprise organization administrators will need to grant access to Claude 3.7 Sonnet in Copilot via a new policy in Copilot settings. Once enabled, you will see the model selector in VS Code, Visual Studio, JetBrains IDes, and immersive chat on GitHub.com. You can confirm availability by checking individual Copilot settings and confirming the policy for Claude 3.7 Sonnet is set to enabled.

Claude 3.7 Sonnet is not currently available in Copilot Free, but you can access it by upgrading to a Copilot Pro plan.

Share your feedback

Join the community discussion to share feedback and tips.

For additional information, check out the docs on Claude Sonnet models in Copilot.

See more

Migration of GitHub Team plan organizations to the enhanced billing platform

Starting today, existing GitHub Team plan organizations will begin to gain access to the enhanced billing platform: a suite of new features designed to help administrators understand and manage GitHub spend for their organizations.

Benefits of the new platform include:

  • Spend transparency – view usage for organizations, repositories, products, and SKUs by hour, day, month, or year
  • Improved control – set budgets to limit spending and configure alerts to stay informed of budget utilization

Enhanced billing platform screenshot

What to expect

All existing Team plan organizations will gain access to the enhanced billing platform by the end of March 2025. Organization owners have been informed via email, and an in-app banner will appear on the billing page in advance of the transition.

Here are some things to know about the transition:

  • Once transitioned, a new Billing & Licensing section will appear in the settings menu.
  • Spending limits will be migrated and renamed as budgets in the new billing platform. For more details about budgets, visit Preventing overspending
  • While the new billing platform will not visually display historical usage, you will be able to download a usage report to get your pre-transition historical usage.

Other important changes

Learn more

For more information, visit Using the new billing platform or join the GitHub Community discussion.

See more

Deprecation of beta GitHub Copilot usage API endpoint

Beginning February 2025, the beta Copilot /usage endpoints will be deprecated.
No new data will be inserted for retrieval via the beta /usage endpoints. This endpoint will be accessible through February, but the 28 day retention policy will remain.

Who’s impacted?

Enterprise organizations with Copilot licenses not yet migrated from the /usage metrics APIs are impacted by this deprecation.

What’s changing and why?

The deprecation of the beta /usage endpoints is a part of GitHub’s effort to deliver more powerful and flexible data offerings for enterprises, organizations, and teams. The new endpoints provide:

  • Visibility into the adoption and consumption of Copilot across various stages of dev lifecycle (from code suggestions to PR reviews), from the team to the enterprise level
  • Expanded scope of metrics, with the addition of GitHub.com Copilot Chat and Copilot for Pull Requests
  • Consistent terminology with the user management API
  • Better visibility into unique users at various drilldowns

Next steps

Ensure your organization is no longer consuming the now deprecated /usage endpoints in any jobs, workflows, and analytics tools.
As an alternative to the beta Copilot /usage endpoints, check out the PowerBI template and the Copilot /metrics endpoints.

Join the discussion in the GitHub community.

See more

Edit the GitHub-owned image on a larger hosted runner

Starting today, customers can change the runner image on larger hosted runners without deleting and re-creating them. You can now update the image and the change will be applied on all future workflow runs to that label. For customers using static IPs, you can change the image on your runner while keeping your IP addresses the same.

Note: partner images cannot be edited at this time and still require the runner to be deleted and re-created.

To edit your runners, follow the steps outlined in our documentation.

See more
View more changes