DeepSeek-V3 is now generally available in GitHub Models

DeepSeek-V3 release on GitHub Models

DeepSeek-V3 is now available in GitHub Models.

DeepSeek-V3 is a 671B parameter Mixture-of-Experts model that excels in mathematics and coding, making it suitable for tasks like solving advanced math problems and generating complex code.

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

Try, compare, and implement this model in your code for free in the playground or via 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.

GitHub Issues & Projects: API support for issues advanced search and more!

Today’s changelog announces API support for issues advanced search, timeline events for issue types, and an update on issue types settings.

You can now use GraphQL and the REST API to perform advanced queries for issues using the AND and OR keywords and nested searches.

For the REST API, you can set the advanced_search parameter to true. Check out the REST API documentation for more details.

http://api.github.com/search/issues?q={query}&advanced_search=true

For GraphQL, you can use the ISSUE_ADVANCED type. Check out the GraphQL documentation for more details.

query {
search(query: "is:issue AND assignee:@me AND (label:support OR comments:>5)", type: ISSUE_ADVANCED, first: 10) {
nodes {
... on Node {
id
}
}
issueCount
}
}

Note that on September 4, 2025, all issue queries will use advanced search by default. This means that after this date:

  • You will no longer need to use the advanced_search parameter for the REST API.
  • The ISSUE GraphQL type will support advanced search.

🕐 Timeline events for issue types

You can now see events in the issue timeline when issue types are added, updated, and removed from an issue.

issue type timeline event

🌇 Issue types for private repositories only will be retired

We are retiring the “Private repositories only” setting for issue types. Over the next week, you will no longer be allowed select this setting to specify an issue type for use only in private repositories. All existing issue types with this setting selected that are marked as Private will be removed on March 26, 2025.

In order to continue using these issue types, you will need to unselect the “Private repositories only” setting in the issue types organization settings page before this date. They can then be edited, disabled, or deleted as needed.

issue types settings

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