Releasesby GlyphCost 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.
Also shipped Jun 25, 2026GitHub in June 2026 →
Genie One enhancements
- Share chats with account users : You can now share Genie One chats with all users in your account as read-only. See Share a chat . New external source connections (Beta) : Chat in Genie One now supports connecting to Gmail and additional Microsoft 365 apps (Teams, Outlook, and Calendar). See Connect to external tools and sources .
Fast mode for Claude Opus 4.7 deprecated, removal on July 24, 2026
After July 24, 2026, requests to claude-opus-4-7 with speed fast will return an error. Anthropic recommends migrating to fast mode on Claude Opus 4.8.
Smart load balancing for deployment set routing is generally available
Smart load balancing, a routing mechanism available with deployment set routing, is now generally available in Starburst Galaxy.
Palantir MCP is generally available
Beginning the week of June 22, Palantir MCP is available across all Foundry enrollments. It enables AI IDEs and agents to design, build, edit, and review end-to-end applications within the Palantir platform.
Ontology MCP is generally available
Ontology MCP is generally available across all Foundry enrollments. It exposes an application's Ontology resources (object types, action types, and functions) as MCP tools for MCP-compatible agents.
Flink UDF external connectivity generally available
UDFs can call external systems such as REST APIs through Connection objects bound with USING CONNECTIONS. Public endpoints on AWS, Azure, Google Cloud; private endpoints on AWS only.
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 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.
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.