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.
Also shipped Jun 29, 2026GitHub in June 2026 →
Dynamic Iceberg table replication (General availability)
Snowflake now supports replication of dynamic Iceberg tables as part of replication and failover groups. Previously, dynamic Iceberg tables were skipped during replication refresh operations. For more information, see Configure replication for Snowflake-managed Iceberg tables .
Databricks SQL version 2026.20 is now available in Preview
Databricks SQL version 2026.20 is now available in the Preview channel. Review the following section to learn about new features, behavioral changes, and bug fixes.
SQL alert task in Lakeflow Jobs is now generally available
The SQL alert task in Lakeflow Jobs is now generally available. Use the task to evaluate a Databricks SQL alert as part of a Lakeflow Job. The task returns its evaluation state as a task output value, so downstream tasks can branch on the result. See SQL alert task for jobs .
Govern LLMs in Unity Catalog with model services (Beta)
You can now govern Databricks-hosted LLMs in Unity Catalog using model services , currently in Beta. A model service is a Unity Catalog securable that represents a governed LLM endpoint, so you can define an endpoint once and share it across workspaces using Unity Catalog privileges, instead of duplicating endpoints per workspace.
Custom Docker images for AI Runtime CLI workloads (Beta)
You can now bring your own Docker container image to AI Runtime CLI ( air ) workloads. This feature is in Beta . Use a custom image when you need specific system library versions, complex dependencies, or a reproducible environment. See Use custom Docker images .
Parquet v2 for Delta Lake tables is generally available
Parquet v2 is now generally available for Delta Lake tables in Databricks Runtime 18.1 and above. Parquet v2 uses advanced encodings, v2 data page headers, and INT64 timestamps to improve query performance and reduce table sizes. To use, set the delta.parquet.format.version table property to 2.12.0 or enable automatic upgrades.
More from GitHub platformEvery GitHub platform release →
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.
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.