Releases: Sidebar navigation and per-asset download counts
You can now scan and navigate release pages more easily with a dedicated sidebar table of contents. We also updated release metadata placement for a more consistent layout so it’s easier to move between entries on long pages. Users with write access can also now see download counts per release asset directly in the Releases UI.
Also shipped Jun 30, 2026GitHub in June 2026 →
Analytical search (Public Preview)
Analytical search, an orchestration capability in Cortex Agents that enables analytical queries over large document collections, is now in Public Preview. Traditional retrieval-augmented generation (RAG) approaches retrieve a small number of passages, which limits their ability to answer questions requiring comprehensive analysis, such as counts...
MATCH_RECOGNIZE is now in Beta
Databricks SQL and Databricks Runtime now support the SQL:2016 MATCH_RECOGNIZE clause for row pattern recognition. Enable the Match Recognize preview in workspace preview settings . See MATCH_RECOGNIZE clause .
Lakehouse Real-Time (Beta)
Lakehouse Real-Time (Lakehouse//RT) is now in Beta . Lakehouse//RT is a serverless SQL warehouse type built for low-latency, high-concurrency workloads, delivering sub-second SQL read queries against Unity Catalog tables.
Gemini Omni Flash in public preview
Released gemini-omni-flash-preview, a high-performance multimodal model designed for high-speed video generation and conversational video editing. Using the Interactions API, you can generate 3--10 second videos at 720p from text descriptions or animate still images, and then conversationally edit and refine the outputs.
Gemini 3.1 Flash Lite Image (Nano Banana 2 Lite) is generally available
gemini-3.1-flash-lite-image is a multimodal model optimized for ultra-low latency, cost-effective image generation and editing, now GA in the Gemini API.
[Launched] Generally Available: Toolboxes in Microsoft Foundry
Microsoft Foundry brings Toolboxes to GA, providing a unified endpoint to invoke the most-used tools in prompt agents and callable outside of prompt agents. Today every agent team hand-assembles its own tool list to solve the same tasks, with no shared ar
More from GitHub platformEvery GitHub platform release →
Restrict issue creation to collaborators only
Repository admins can now restrict issue creation to collaborators with write access. This gives you more control over who can open issues and helps reduce unwanted issue creation, while keeping issue workflows available to the people who actively maintain and contribute to the project.
Issue fields are now generally available
Issue fields are now generally available for all GitHub organizations on Free, Team, Enterprise, and GitHub Enterprise Cloud with data residency plans and will ship in GitHub Enterprise Server 3.23.
Cost center limit increased to 1,000 per enterprise
You can now create up to 1,000 cost centers per enterprise, up from 500. Enterprises that model hundreds or thousands of business units, departments, or product groups can now represent that full structure in GitHub, instead of exporting usage data into a homegrown system to fill the gap.
Saved views for repository issues – Public Preview and adjustable row heights in projects
Saved views for repository issues Repository Issues pages now support saved views, making it easier for teams to create and share filtered views of their issues. With saved views, anyone with triage access or above can create shared views like “Unassigned bugs”, “Needs triage”, or “Customer-reported issues”.
Cost centers now support enterprise teams
Cost attribution across your enterprise can now follow your team structure. You can add enterprise teams as resources in a cost center, and all usage incurred by team members is attributed to that cost center.
Restrict who can dismiss reviews in rulesets
You can now restrict who can dismiss pull request reviews directly in GitHub repository rulesets. This capability is generally available and gives you precise control over who can clear an approval before changes merge. The setting lives alongside the other review options in the Require a pull request before merging rule.
New pull requests dashboard is now generally available
The refreshed pull requests dashboard is now generally available at github.com/pulls . It gives you a single home to track, prioritize, and act on the pull requests that need your attention, whether you’re an individual contributor or a manager working across many teams and projects. This experience was previously in public preview.
Per-user states for multi-user budgets in the REST API
You can now retrieve every user’s progress against a multi-user budget from a single REST API endpoint. This makes it much faster to find who is close to their limit across a large enterprise. Previously, you had to make one API call per user to check per-user consumption, and you couldn’t filter by how much of the budget someone had used.