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.

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
View all changes