Releasesby GlyphCost 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.
Also shipped Jun 26, 2026GitHub in June 2026 →
SQL queries as logical tables in semantic views (General availability)
You can now use an SQL query (rather than a physical table) as a logical table in a semantic view. This lets you define logical tables based on joins, transformations, or any SQL expression without creating a separate view first.
Support for variables in semantic views (General availability)
You can now define variables in a semantic view to parameterize facts, dimensions, and metrics. Variables let you customize calculations at query time without changing the view definition. Define variables when you create a semantic view using the VARIABLES clause in the CREATE SEMANTIC VIEW command, or by adding a variables key in the YAML specification .
Microsoft Dynamics 365 connector (GA)
The managed Microsoft Dynamics 365 connector in Lakeflow Connect is now generally available. The connector allows you to ingest CRM and ERP data from Dynamics 365 into Databricks using Azure Synapse Link. See Microsoft Dynamics 365 connector .
Metric view parameters are now in Public Preview
You can now define parameters in metric views to bind values at query time, serving many query variants from a single definition instead of maintaining a separate metric view per variant. See Use parameters with metric views .
Databricks Runtime 19 (Beta): June 26, 2026
Behavioral changes Environment variable availability restricted in standard access mode : In standard access mode , only a predefined set of environment variables is available to the Spark engine and init scripts.
Previewing GPT-5.6 Sol: a next-generation model
OpenAI previews GPT-5.6 Sol, a next-generation model with stronger capabilities in coding, science, and cybersecurity, paired with its most advanced safety stack.
More from GitHub platformEvery GitHub platform release →
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 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.
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.
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.