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

Copilot Chat now supports pasting links

An illustration of a GitHub issue link with a purple and blue background. A URL is displayed in a browser bar at the top, with a dark notification box shows below it, all next to the Copilot logo.

Issues, discussions, and pull requests – these are all important pieces of context when building in GitHub. Now, you can reference these within Copilot Chat. Simply paste a link into the chat and Copilot will do the rest!

How it helps you

  • 📂 Multi-repository support: want to compare a pull request from one project with a discussion from another? No problem!
  • 🏷️ Intuitive navigation: maybe you pasted a link, got up to make a coffee, and forgot what you were doing. With chips in the chat context, you don’t need to worry – it will always be clear what you’ve added.
  • ⌨️ Context-building at your fingertips: let Copilot support you and integrate your work by focusing on the specific problems you want to address.

We like to think that GitHub files and Copilot are both great, and they’re even better when they come together. The power of Copilot and the fountain of knowledge in your repositories will collectively help you do amazing things. We know it.

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

See more

GitHub Actions hosted runner fleet now includes 96 vCPU larger runner

GitHub Actions 96 vCPU larger runners are now generally available. Customers in need of bigger, more powerful machines to run their workloads can use this runner to reduce runtime on their longer GitHub Actions builds.

This runner is an x64 machine and you can use any of our existing GitHub-owned Linux and Windows images on these runners. Our entire advanced feature set works with the new runner: static IPs, network configurations, autoscaling, and runner groups.

What are the machine specs?

  • vCPU: 96
  • RAM: 384 GB
  • SSD: 2040 GiB

Get started today

To get started, create a new, larger runner and choose the 96-core option in the Size console in the UI. Learn more about how to set up larger runners in our documentation. For pricing information on these larger runners see the billing for GitHub Actions page.

See more

Dependabot version updates now support Helm

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

See more

Evolving GitHub Issues and Projects

Announcement of the new issues experience with a screenshot

We continue to improve how teams can plan, track, and manage their work on GitHub. Following our public preview in January, we’re thrilled to announce the general availability of sub-issues, issue types, advanced search, and increased item limits in GitHub Projects 🎉. Here’s a detailed look at how these new capabilities can help transform your workflow.

🏗️ Bring structure to your issues with issue types

Imagine your team is beginning a new feature. The first step is to create a new issue and assign it a Feature issue type to designate it as a larger piece of work.

Consistency is key when managing multiple repositories within an organization. Issue types provide a standardized way to classify and manage your issues. With a shared language across all repositories, you can quickly gauge the progress of your bug backlog, identify high-level initiatives, and understand the breakdown of work in any project. Imagine you’re viewing the index page of a repository, and all issues are clearly categorized by type. Or you’re using project insights, and it’s easy to understand the type of work your team’s been spending their time on. This clarity makes it easier to prioritize tasks and effectively allocate effort.

Want to implement issue types in your organization? Learn more about issue types.

🔨 Break it down with sub-issues

Once you’ve created your feature issue, it’s time to break it down into smaller, manageable pieces of work using sub-issues. This lets you traverse the hierarchy of issues, helping you track progress and understand the remaining work at a glance.

Sub-issues provide a nested structure that integrates seamlessly with your projects, giving you a visual representation of progress. Whether you’re coordinating a team or working solo, sub-issues ensure nothing falls through the cracks.

Curious to see how sub-issues can help streamline your workflow? Learn more about sub-issues.

As work progresses, finding the exact issues you need can be simplified with advanced search.

Using AND, OR, and parentheses for nested searches, you can build complex filters to pinpoint the exact set of issues you’re looking for from the repository or the global issues dashboard. For example, you can search for issues related to your feature with the query is:issue type:Bug OR type:Feature. This helps you quickly and efficiently find the next issue to pick up.

Ready to refine your searches? Learn more about advanced search.

📈 Expanding project limits

All your issues can also be laid out in a GitHub Project. We’ve listened to your feedback that you want space for more issues in your projects, so we’ve expanded the limits from 1,200 to a huge 50,000 items per project! 🎉

With today’s general availability announcement, we’ll be removing the opt-out option in the coming weeks. Moving forward, we’ll also make increased limits your default mode.

✨ Enhancements to the GitHub Issues UI

We’ve also updated the GitHub Issues UI to make it faster and more intuitive. These updates are designed to enhance your experience without introducing new patterns that could slow you down. Some key improvements include:

  • A new filter bar with autocomplete and syntax highlighting on the repository and issues dashboard pages.
  • A create more option for faster issue creation, allowing you to quickly return to the creation screen.
  • An alphabetical ordering of issue forms and templates based on file name, helping you find and set the right order.
  • A copy link button for easily sharing the URL of an issue.
  • An increased load more event count from 50 to 150 on long issues.

👀 Your feedback matters

We value your thoughts and feedback. Join the conversation to share your experiences and suggestions.

Explore how GitHub Issues and Projects can enhance your project planning, check out our roadmap, and dive deeper into the features in our documentation.

Thank you for being a part of our journey to improve GitHub Issues and Projects. We can’t wait to see what you build next! 🎉

See more

Push rule delegated bypass and custom property regex support are generally available and repository policy delegated bypass is in preview

Push rules are great for maintaining the integrity of your codebase by preventing unauthorized changes to critical files such as actions workflows. However, they can sometimes slow down the development process. With delegated bypass, developers can easily request exceptions to these push rules. This process is reviewed and audited within GitHub, helping to ensure that every exception is properly documented and approved.

We are also bringing a preview of the delegated bypass flow to repository policies. This provides additional reviews when deleting repositories as well as visibility changes to prevent accidents and help ensure good governance.

Finally we’re also introducing regex support for custom properties.

Push rule delegated bypass

Unlock efficiency with our push rule delegated bypass. Now, developers can:

  • Request push rule exceptions directly within GitHub.
  • Ensure every request is reviewed and audited for maximum transparency.
  • Receive notifications via email for real-time updates on approval status.

Learn more about push rule delegated bypass in the documentation.

Repository policy delegated bypass in preview

Extend the delegated bypass functionality to your repository policies. This feature is designed to:

  • Offer additional reviews for critical actions such as deleting repositories or changing visibility settings.
  • Prevent accidental changes that could compromise your project.
  • Submit bypass requests directly from the repository’s danger zone.

Learn more about repository policy delegated bypass in the documentation.

Custom properties regular expression matching

When using Text types for custom properties you can require new values to match a regular expression pattern, like an email address.

  • Test your regex pattern against sample values from the new property creation screen.
  • Supports the RE2 syntax, for more information see the syntax guide.

Join the discussion and share your feedback, questions, and thoughts within our GitHub Community discussion.

See more

DeepSeek-V3-0324 is now generally available in GitHub Models

DeepSeek-V3-0324 release on GitHub Models

DeepSeek-V3-0324 is now available on GitHub Models.

DeepSeek-V3-0324 is a 671B parameter Mixture-of-Experts (MoE) model that builds notable updates on top of its predecessor, DeepSeek-V3. These include enhanced reasoning capabilities and improved function calling accuracy. This model also excels in Chinese writing proficiency and includes advanced search capabilities for Chinese.

Note: DeepSeek-V3 will be deprecated on Friday, April 11th, 2025. We recommend transitioning to DeepSeek-V3-0324 to take full advantage of its enhanced features.

Try, compare, and implement this model in your code for free in the playground or through the GitHub API. Compare it to other models using side-by-side comparisons in GitHub Models.

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

See more

Reload responses with other Copilot models on github.com

Image of Copilot next to a model selection menu

The immersive mode of Copilot Chat now gives you more choices when reloading your responses.

What’s new?

You can now easily regenerate Copilot responses using a different model. Simply click the retry button underneath Copilot’s response. Copilot will process the same prompt by your chosen model while maintaining all previous conversation context. You can also view previous responses and compare model output.

How it helps you

  • 🧩 Stuck on a complex problem? Switch to a more powerful model for deeper reasoning.
  • ⚡ Need a quick response? Reload with a faster model when speed matters.
  • 💻 Working with code? Switch to a model optimized for programming.
  • 🎨 Fine-tuning creative work? Try different models to explore alternative approaches.

This feature is perfect for when you need a different perspective or more specialized capabilities. Seamlessly blend the strengths of various models into a single conversation. Enjoy more intelligence, more flexibility, and more control – all while staying in the flow.

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

See more

Security campaigns are now generally available to help address security debt at scale

Security campaigns are now generally available

Security campaigns with Copilot Autofix are now generally available. As part of GitHub Code Security, you can use security campaigns to prioritize and rapidly reduce your backlog of application security debt. Copilot Autofix generates contextual explanations and fixes for historical code scanning alerts in a security campaign, which help developers and security teams collaborate to fix vulnerabilities with speed and confidence.

With the help of GitHub’s CodeQL and Copilot Autofix, it has never been easier to prevent new vulnerabilities from being added to your code. However, if you don’t address vulnerabilities discovered in already-merged code, security debt can build up and pose a serious risk to deployed applications.

A security campaign on GitHub can contain a large number of code scanning alerts, prioritized by your security team to be fixed within a chosen timeframe. When a campaign is created, Copilot Autofix automatically suggests fixes, and developers who are most familiar with the code are notified. From there, they can review the fixes, open pull requests, and remediate security debt. Security teams can monitor the progress of the campaign and track the number of fixed alerts. Using security campaigns, security and developer teams work together with Copilot Autofix to remove security debt in targeted efforts aimed at maximizing impact by focusing on the alerts that matter.

Starting today, you can also access these new features to plan and manage security campaigns more effectively:

  • Draft security campaigns: Security managers can now iterate on the scope of campaigns and save them as draft campaigns before making them available to developers. With draft campaigns, security managers can ensure that the highest priority alerts are included before the work goes live.
  • Automated GitHub issues: Security managers can optionally create GitHub issues in repositories that have alerts included in the campaign. These issues are created and automatically updated as the campaign progresses and can be used by teams to track, manage, and discuss campaign-related work.
  • Organization-level security campaign statistics: Security managers can now view aggregated statistics showing the progress across all currently-active and past campaigns.

Security campaigns are available for users of GitHub Code Security on GitHub Enterprise Cloud. For more information about security campaigns, see About security campaigns in the GitHub documentation.

If you have any feedback on security campaigns, join the discussion in GitHub Community.

See more

Changes to the repository object in push webhook

We are updating the url field for push webhook events.

Previously, both html_url and url returned the same link, unlike other events like pull_request.

Now, html_url will return the repository URL (e.g., https://github.com/<org>/<reponame> )  and url will provide the API URL (e.g., https://api.github.com/repos/<org>/<reponame>).

Join the discussion in GitHub Community.

See more

Copilot code review now generally available

Copilot code review is now generally available!

Code review is one of the most critical parts of software development, but manual code reviews 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 fixes. This means you can start iterating on your code while waiting for a human review, helping you keep your code repositories more maintainable and focused on quality.

In just over a month since we launched the public preview, over 1 million developers have already used Copilot code review, and the response has been incredible.

Check it out in action, in both Visual Studio Code and GitHub:

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

Copilot code review is available to all paid Copilot subscribers. Organizations and enterprises can enable it through the Copilot in github.com policy.

What’s next

We’re continuously improving Copilot code review. Today we’ve added support for C, C++, Kotlin, and Swift in public preview and we’ll add support for HTML and txt early next week.

To learn more, check out our code review 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

Announcing GitHub Copilot Pro+

Today, we’re introducing GitHub Copilot Pro+, a new individual tier for developers who want to take their coding experience to the next level.

Enjoy all the features you love from GitHub Copilot Pro along with exclusive access to the latest models (GPT-4.5 is available today), priority access to previews, and 1500 premium requests per month when they go live on May 5th. This is in addition to the unlimited requests for agent mode, context-driven chat, and code completions that all paid plans have when using our base model.

To get started, purchase GitHub Copilot Pro+ today and don’t miss out on the other Copilot updates shared in our announcement blog.

Stay tuned for updates as we work to continuously enhance your developer experience. Also, please share any feedback in GitHub Community.

See more

Multiple new models are now generally available in GitHub Copilot

Anthropic Claude 3.7 Sonnet, Claude 3.5 Sonnet, OpenAI o3-mini, and Google Gemini Flash 2.0 are now generally available in GitHub Copilot. With this change, these models are promoted from preview release terms to generally available release terms. This extends indemnification for IP infringement to code generated using these models in Copilot Chat and agent mode.

Copilot hero image

  • Claude 3.7 Sonnet, Anthropic’s most advanced model to date, excels in development tasks that require structured reasoning across large or complex codebases.
  • Claude 3.5 Sonnet remains a good choice for everyday coding support.
  • OpenAI o3-mini is a fast, cost-effective reasoning model designed to deliver coding performance while maintaining lower latency and resource usage.
  • Gemini 2.0 Flash is Google’s model optimized for fast responses and multimodal interactions.

Learn more about the models available in Copilot in our documentation and get started with Copilot today.

See more

github-mcp-server is now available in public preview

The official open source GitHub MCP Server

Today we’re releasing a new open source, official, local GitHub MCP Server. We’ve worked with Anthropic to rewrite their reference server in Go and improve its usability. The new server contains 100% of the old server’s functionality plus the ability to customize tool descriptions, support for code scanning and a new get_me function that improves the natural language user experience when asking the LLM things like: “Show me my private repos.”

To get started, visit the repository and learn how to set up the GitHub MCP Server, which is now supported natively in VS Code.

Model Context Protocol (MCP) is an AI tool calling standard that has been rapidly gaining adoption over the past few months. MCP tools give LLMs a standardized way to call functions, look up data, and interact with the world. Anthropic created the protocol and built the first GitHub MCP server, which grew to be one of the most popular MCP servers in the expanding ecosystem. We are excited to take ownership of the server and continue its development.

Join the discussion within GitHub Community.

See more

GitHub Copilot in VS Code March release (v1.99)

The latest updates to GitHub Copilot in the March 2025 release of Visual Studio Code (v1.99) include upgrades to agent mode, such as the addition of MCP support, enabling the use of models through API keys, and more. Read on for more release highlights.

Agent mode is now available in VS Code stable

  • Rolls out to users starting today and continuing through the coming weeks. Make sure you’re on the latest VS Code version. Can’t wait? Update to the latest of version of VS Code and manually enable agent mode.
  • Includes Model Context Protocol (MCP) server support to let you choose from hundreds of specialized tools for your agent flow.
  • Equipped with new built-in tools, such as for fetching web content and finding symbol references.

UX improvements help you work faster and stay focused

Limitless model choice

And that’s not all. Check out the VS Code March 2025 release notes for the full scoop. Happy coding!

See more

Dependency graph supports all purl-identified package ecosystems

GitHub’s dependency graph now supports a wider range of package ecosystems, including transitive path information and the registered name of the ecosystem. This change increases the accuracy and usefulness of GitHub’s dependency insights, SBOMs, and API results.

The Package URL project provides a registry of software package ecosystems, with a standardized format for package type, namespace, version, and human-readable identifiers. With this release, graphs posted to the dependency submission API that include purl identifiers will now:

  • Correctly preserve transitive and direct relationships, if they were submitted.
  • Show the package ecosystem name in the Dependency Graph insights page.
  • Include the submitted package url in the GraphQL DependencyGraphDependency object, in the field packageUrl.

For searching and filtering, note that the top-level ecosystem type for all purl-identified packages is now other. These packages used to have the unknown type.

To begin using this feature, add a dependency submission action for a purl-supported package ecosystem you’re using in your repository. Then navigate to the repository’s Insights tab and select Dependency graph.

The dependency graph insights page, showing an ecosystem filter of other with three packages in a list.

See more

GitHub Enterprise Server and ESXi 8.0 support

VMware ESXi 8.0 hypervisor support is now available for GitHub Enterprise Server (GHES) 3.16.0, 3.15.4, 3.14.9, 3.13.12, and later. Until now, GHES was supported on ESXi versions 5.5 to 7.0. However, ESXi 7.0 is reaching the end of general support by October 2025.

If your GHES installation is on VMware ESXi 7.x or an earlier version, you can now use the ESXi 8.0 hypervisor. For more information about installing GHES on VMware, see install on VMware.

See more

Pull request merge experience – April 3 update

Today we’re announcing recent fixes and enhancements to the improved pull request merge experience that became generally available earlier this month.

🆕 Status checks grouping preference

You can now choose to show the list of status checks as a single flat list or grouped by status. Click the settings gear and choose either “Group by status” (the default) or “No grouping“.

Image showing the new merge experience status checks section expanded with a new settings gear menu opened and showing 2 options for controlling how status checks are grouped (no grouping or grouping by status)

Recent fixes

Some of the noteworthy fixes that have landed in the last few weeks:

  • The time since a status check started (e.g. Started 2s ago) now updates consistently.
  • The Draft section was previously hidden for users without write access, making it difficult to know that the pull request was not ready for review.
  • A tooltip was previously not appearing when hovering over a truncated status check’s name, making it difficult to differentiate status checks with similar, long names.
  • Various fixes related to updating the pull request branch by rebasing.
  • Various improvements to performance, especially when there were a significant number of status checks.

Get help

To ask questions or provide feedback, join the discussion within GitHub Community.

See more

GitHub Issues: Dashboard updates

🌐 New and improved Issues dashboard

You’ll now see an updated Issues dashboard page at github.com/issues, allowing you to easily find and create issues across repositories and organizations. This page can be accessed through the global navigation menu under Issues.

These improvements include:

  • A new filter bar with autocomplete and syntax highlighting to make building searches fast and easy.
  • The ability to perform advanced searches using AND and OR keywords as well as nested searches. For example, (org:github AND type:bug) OR (org:dizzbot AND has:sub-issue) allows you to find issues across multiple organizations. Note that a space between filter fields acts as an AND search.
  • The ability to create issues directly from this page by selecting New issue and choosing a repository.
  • A new Recent activity view in addition to the Created by me, Assigned to me, and Mentioned views. This view finds relevant issues that involve you.

Issues dashboard "Recently viewed" page

✍ Tell us what you think!

Join the discussion in GitHub Community.

See how to use GitHub for project planning with GitHub Issues, check out what’s on the roadmap, and learn more in the documentation.

See more

Copilot Chat on github.com adds support for images

Image showing a command to convert an architecture diagram photo into a Markdown file

The immersive mode of Copilot Chat on GitHub now supports image upload and analysis when using 4o, adding powerful multimodal capabilities to your development workflow. This feature was previously exclusively available on VS Code and Visual Studio.

✨ What’s new?

  • 🔗 Image upload & analysis: Upload, paste, or drag images directly into Copilot conversations.
  • 🧠 Visual context understanding: Ask questions about code screenshots, UI designs, system diagrams, and more.
  • ⚡ Image to code: Generate HTML files based on images and preview them in the side panel.

With so much of the software development lifecycle happening through images, diagrams, and other visual artifacts, we hope this release brings you closer to communicating and collaborating with Copilot in ways that mirror how you naturally think and work.

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

See more

Scheduled Codespaces maintenance – April

Codespaces will be undergoing maintenance in all regions starting from 17:00 UTC on Wednesday, April 2 to 17:00 UTC on Thursday, April 3. Maintenance will begin in Southeast Asia, Central India, Australia Central, and Australia East regions. Once it is complete, maintenance will start in UK South and West Europe, followed by East US, East US2, West US2, and West US3. Each batch of regions will take approximately three to four 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
View more changes