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

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

Copilot Autofix is available for more code scanning alerts

Copilot Autofix helps you fix code scanning alerts and avoid introducing new security vulnerabilities by using large language models to suggest potential fixes.

We recently expanded the range of CodeQL security alerts where Copilot can suggest an autofix, covering a group that accounts for 29% of all CodeQL alerts. This expansion led to an 8% overall increase in alerts with an available autofix and a 270% increase in autofixes for this specific group of improved alerts. With more autofix suggestions, you can resolve security issues identified by CodeQL more easily—either by applying Copilot’s suggested fix directly or using it as a starting point for your own edits.

We made these improvements by analyzing our usage data to understand the most common types of alerts where Copilot was not suggesting fixes and then made a targeted effort to improve autofix for these alerts. Read more about the testing process that GitHub uses to identify the quality of autofix suggestions.

We continuously evaluate the performance of CodeQL and Copilot Autofix, so look for more improvements in the future.

See more

GitHub Copilot in JetBrains IDEs: @project context and commit message suggestions

The GitHub Copilot plugin for JetBrains IDES now helps you ask questions about your entire codebase, via @project, and Copilot can help you out even more by generating commit message suggestions.

@project context

With @project context, you can ask any question you have about your project, and Github Copilot will read your entire project’s codebase and return detailed answers with references to relevant files and symbols. @project context helps you find the code you’re looking for, understand how functionality is implemented, and much more.

Commit message suggestions

Now GitHub Copilot in JetBrains will generate commit messages for you, helping you craft informative commit messages and saving you that extra bit of time every day. 

UX improvements & bug fixes

This update also includes a few other UX improvements:

  • Chat conversations are now ordered by last modified time.
  • We fixed a bug where chat conversation history was lost after signing out.
  • We fixed color display issues when switching system themes between dark and light. 

Get started and join the discussion

Try out the latest version of the GitHub Copilot plugin and share your thoughts in the GitHub Community. We’d love to hear your feedback!

 

See more

Dependabot helps users focus on the most important alerts by including EPSS scores that indicate likelihood of exploitation, now generally available

Dependabot alerts now feature the Exploit Prediction Scoring System (EPSS) from the global Forum of Incident Response and Security Teams (FIRST), helping you better assess vulnerability risks.

EPSS scores predict the likelihood of a vulnerability being exploited, with scores ranging from 0 to 1 (0 to 100%). Higher scores mean higher risk. We also show the EPSS score percentile, indicating how a vulnerability compares to others.

For example, a 90.534% EPSS score at the 95th percentile means:

  • 90.534% chance of exploitation in the next 30 days
  • 95% of other vulnerabilities are less likely to be exploited

You can use EPSS scores to help prioritize dependency vulnerabilities based on exploit likelihood. Only ~0.5% of vulnerabilities have an EPSS score above 50%. This makes EPSS a powerful tool for prioritization based on exploitation likelihood, especially when used in conjunction with exploitation severity (CVSS). For more information on using EPSS and/or CVSS for vulnerability prioritization, check out FIRST’s EPSS user guide.

This feature is available on GitHub.com today, and will be available in GitHub Enterprise Server staring with version 3.17.

Learn more in FIRST’s EPSS User Guide.
Join the discussion within GitHub Community.
Read more about viewing, sorting, and filtering Dependabot alerts in GitHub’s Dependabot docs.

See more

Enhanced billing platform for Free plan for organizations

Starting February 4, 2025, new GitHub Free plan customers will gain access to the enhanced billing platform: a suite of new features designed to help administrators understand and manage GitHub spend for their organization.

Benefits of the new platform include:

  • Spend transparency: view usage for organizations, 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

Screenshot of the metered usage graph in the Mona-free-organization

What to expect

Existing Free plan customers 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

Announcing the General Availability of GitHub Copilot Extensions

Copilot Extensions GA

Your tools. Your workflows. All within Copilot Chat.

GitHub Copilot Extensions are now generally available for users across all Copilot license tiers. With Copilot Extensions, you can integrate and prompt your favorite tools directly in Copilot Chat using natural language wherever you develop, including Visual Studio Code, Visual Studio, JetBrains IDEs, and GitHub.com. Copilot Extensions on GitHub Mobile will be generally available in the coming weeks.

Copilot Extensions help you stay in your workflow, with context-aware assistance from your favorite tools right at your fingertips. Today’s marketplace is home to a wide range of extensions, from Perplexity to Stack Overflow, to Docker and Mermaid Chart. Developers can unlock productivity gains with extensions in minutes. For example, Arm’s extension streamlines cloud adoption and migration, enabling developers to build, test, and deploy software on Arm-based servers while seamlessly leveraging Arm’s efficient, scalable, and high-performance architecture.

Explore these extensions and more on the GitHub Marketplace to bring new contexts and capabilities into the chat. All you need is access to GitHub Copilot to get started. 🚀

Building GitHub Copilot Extensions

Our platform also empowers you to build your own public or private extension depending on your requirements. This flexibility allows you to develop extremely customized extensions for your enterprise or organization, or develop general applications that can serve thousands of developers. The comprehensive Copilot Extensions toolkit provides you with centralized code samples and tools to help you build high quality extensions.

Alongside General Availability, we’re introducing OpenID Connect (OIDC) support for builders. This replaces the X-Github-Token auth model with native third-party tokens, reducing API round trips, and improving security. Instead of verifying GitHub tokens on every request, integrators receive pre-exchanged tokens tailored to their system, enabling direct authentication and authorization. This lowers latency, simplifies identity mapping, and aligns with GitHub’s existing OIDC workflows for Actions.

Builders have several ways to develop customized extensions, including:

  • Copilot skillsets, a faster, lightweight implementation option
  • Context passing, a capability that helps extensions benefit from a user’s local editor context for more tailored responses

Ready to contribute to our growing ecosystem? Get started with our Copilot Extension builder docs.

👀 What’s next?

Our general availability is only the starting point for agentic capabilities. We’re continuing to reimagine AI assisted workflows, with recent releases like agent mode and explorations around Project Padawan. These innovations only scratch the surface of what is possible with GitHub and AI agents. Continue being a part of the conversation by providing feedback as you try out extensions. ⭐

See more

New GPT-4o Copilot code completion model now available for Copilot in JetBrains IDEs

The new code completion model announced yesterday is available today to all JetBrains users of GitHub Copilot.

To get started, ensure that you are on the latest stable release of the extension (v1.5.35 or above). Click the Copilot icon in the JetBrains IDE of your choice and select Edit model for Completion. This will open the GitHub Copilot settings, where you can switch between models.

See more

Repositories – Enterprise rules and custom properties updates

Enterprise rules and custom properties are getting updates as part of the current public preview, as well introducing a new search and filter experience for custom properties.

Custom properties

Screenshot depicting new filter options available

There are new search and filtering options for custom properties now generally available to ensure you can easily find the right property.

  • Managed by allows you to limit your result by the organization or enterprise who manages the property.
  • Property type allows you to limit your result by the available type of properties.
  • Text allows you to limit your result by the context of the property name or values.

Enterprise custom properties

Screenshot of custom property promotion screen

Enterprise custom properties as part of the current preview can now be promoted from an organization to an enterprise property. This ensures properties configured in one organization are available across all organizations in an enterprise.

Enterprise code rulesets

Screenshot of configuring enterprise workflow rule

Required workflows are now available as a new rule in the enterprise code rules preview. This will allow you to target workflows across specific organizations and repositories with a single workflow file managed at the enterprise.

Note: GitHub Enterprise Cloud with data residency support for the enterprise workflow rule will be coming soon.

Join the discussion within GitHub Community.

See more

Recent improvements to Artifact Attestations

We released a collection of improvements to Artifact Attestations to make the verification of attestations easier and more consistent.

Artifact Attestations let you create provenance signatures, which provide an unforgeable paper trail that links your artifact back to its originating workflow run. By verifying the signature, you can gate deployments to ensure that what you deploy is exactly what you built, guaranteeing that the artifact has not been tampered with.

Today we are announcing multiple improvements based on the user feedback we have received:

  • Attestation verification defaults to build provenance: Build provenance is just one type of information that can be attested to an artifact. It provides a verifiable trail that links the artifact back to its originating workflow run, ensuring its authenticity and integrity. However, other types of information can also be attested to an artifact, for example a Software Bill of Materials (SBOM). Attestations can be verified by running gh attestation verify using the GitHub CLI. Previously, verification succeeded as soon as there was any attestation associated with the artifact. However, we observed that provenance is verified in the vast majority of cases. Therefore, we altered the CLI to default to provenance when no predicate type is specified. This change ensures that verification does not pass merely because, for example, an SBOM was attested to the artifact. To verify an SBOM, the predicate type must be explicitly supplied as a parameter using gh attestation verify with the --predicate-type parameter.
  • CLI outputs evaluated policies during verification: When verifying an attestation, the CLI now outputs all the policies it evaluated to determine whether the verification succeeds or fails. This increases transparency, making it easier to understand the reasons behind the verification outcome.
  • Attest actions support multiple subjects: Following the release to support attesting multiple subjects, we have enhanced our attest, attest-build-provenance and attest-sbom actions to also accept a checksum file that contains a list of artifacts and their corresponding digests as input.
  • Attestation verification is now monotonic: This means that once verification passes for an artifact, the addition of another attestation cannot change that status. Verification now succeeds if at least one attestation passes verification. This ensures that downstream processes, such as gated deployments, are not affected for any legitimate build that has a valid provenance attestation, even if someone adds another attestation that is bad or malformed.

For more information about Artifact Attestations, see Using artifact attestations to establish provenance for builds in the GitHub documentation. If you have any feedback on Artifact Attestations, join the discussion in the GitHub Community.

See more

New GPT-4o Copilot code completion model available now in public preview for Copilot in VS Code

Header introducing GPT-4o Copilot model

A new code completion model, GPT-4o Copilot, can now be enabled by VS Code users.

This new model based on GPT-4o mini has additional training on over 275,000 high-quality public repositories in over 30 popular programming languages. As a result, you can expect this model to provide more accurate suggestions and to have better performance.

Getting started with GPT-4o Copilot in VS Code

To get started, open the Copilot menu in the VS Code title bar, select Configure Code Completions... > Change Completions Model.... Alternatively, open the Command Palette and select GitHub Copilot: Change Completions Model....

GPT-4o Copilot access notes

If you are a Copilot Business or Enterprise user, you will first need your administrator to enable this model for your organization by opting in to Editor preview features in the Copilot policy settings on github.com.

If you are a Copilot Free user, using this model will count toward your 2,000 free monthly completions.

The model will also be available soon to Copilot users in all JetBrains IDEs.

Please share your feedback as you try out the new model. It will help us improve the experience for all Copilot users.

See more

GitHub Issues & Projects – February 18th update

Today’s changelog brings you a snappier issue creation flow in projects, the ability to convert checklist items to sub-issues, required fields on private repositories, and important updates on tasklist blocks and single issue templates.

✍️ Improved issue creation flow in projects

Creating a new issue from a project is now easier than ever. Previously, when you started typing in an issue title in a project, the default was to create a draft issue. However, we’ve heard from user feedback that the primary
desired use case is to create an issue instead of a draft. Now, with this update, you can directly create a new issue by pressing Enter or create a draft with Cmd / Ctrl + Enter.

🔒 Required fields on issue forms for private repositories

You can now specify required fields on issue forms in private repositories, which ensures that contributors provide essential information before submitting an issue.

➡️ Convert checklist items to sub-issues

You can now convert checklist items in issues directly to sub-issues, making it easier to turn draft or to-do tasks into actionable work items.

🌇 Tasklist blocks will be retired and replaced with sub-issues

The private preview feature, tasklist blocks, will be retired on April 30, 2025. Your feedback from the private preview has been invaluable, helping us shape the release of sub-issues, the replacement for tasklist blocks.

Sub-issues provide a dedicated section within each issue, making it easier to track related work without relying on Markdown. You can manage up to eight levels of hierarchy within a single issue and monitor progress directly in your projects.

Migrate to sub-issues

We recommend migrating your tasklists to sub-issues before the retirement date.

To migrate, first simply remove the tasklist Markdown syntax to display the list as an issue checklist.

- ```[tasklist]
- - [ ] task 1
- - [ ] https://github.com/github/github/issues/123
- ```
+ - [ ] task 1
+ - [ ] https://github.com/github/github/issues/123

Then, use the Convert to sub-issue feature to convert desired issues or checklist items into sub-issues.

After April 30, 2025, remaining tasklist blocks will no longer be rendered and will instead be converted to raw Markdown. The Tracked and Tracked by fields on projects will no longer be available.

🌅 Single issue templates (ISSUE_TEMPLATE.md) will be retired

The legacy ISSUE_TEMPLATE.md feature will be retired on March 30, 2025. As a replacement, we encourage creating an ISSUE_TEMPLATE/ subdirectory in any of the supported folders to store multiple issue templates. You can then use the template query parameter to specify which template should populate the issue body. For more details, see the documentation.

After March 30, 2025, repositories still using ISSUE_TEMPLATE.md will default to a blank issue form, allowing users to start fresh when creating issues.

✨ Additional improvements

On top of the many bug fixes we’ve shipped, we’ve also introduced the following improvements:

  • You can now create new milestones directly from the milestone picker in any issue.
  • The issue template selection will now be bypassed if only one template is available and the blank issue template is disabled.
  • You can now create and edit iteration fields via the ProjectV2 GraphQL API.
  • We’ve introduced a move dialog in Projects, allowing you to rearrange items and views with precision. You can move views from a tab’s view options menu, while items can be moved through the row actions menu. This allows users who rely on screen readers, keyboards, and other assistive technology to use projects more accessibly.

✍ Tell us what you think!

Join the discussion within the 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
View more changes