Releasesby GlyphGitHub Enterprise adds credential inventory exports
Enterprise owners can now export a complete inventory of every credential that can access their enterprise (e.g., SSH keys, classic and fine-grained personal access tokens, OAuth App access tokens, and GitHub App user-to-server and installation tokens).
Also shipped Sep 21, 2026GitHub in September 2026 →
BigQuery Studio query results pane shows recent run history
The Query results pane now shows a short history of recent runs for a query, including multi-statement queries, without switching to the Job history tab. It is generally available.
The query history system table is now generally available
The system.query.history system table is now generally available. Use it to access account-wide records for queries run on SQL warehouses or serverless compute, including execution status, duration metrics, and query source. See Query history system table reference .
Cortex AI Function Evaluation for measuring quality (Public Preview)
Snowflake Cortex AI Function Evaluation is now available in public preview, enabling customers to measure the output quality, cost, and token usage of custom AI Functions and Cortex AI calls against labeled datasets.
Cortex AI Function Optimization for more efficient AI implementations (Public Preview)
Snowflake Cortex AI Function Optimization is now available in public preview, enabling customers to automatically search across prompts and models for improved implementations of custom AI Functions.
Cortex Agents Compact API (Preview)
The Cortex Agents Compact API is now available in preview. Use the agent:compact endpoint to summarize a conversation and pass the compact representation to subsequent agent:run requests. Compacting conversation history reduces token consumption and helps conversations stay within the model context window.
You can now use the AlloyDB Columnar Engine as a read-optimized, in-memory cache for HNSW vector indexes
You can now use the AlloyDB Columnar Engine as a read-optimized, in-memory cache for HNSW vector indexes. This feature is generally available ( GA ). It accelerates vector search performance and increases queries per second (QPS) for vector workloads. For more information, see Accelerate queries with the Columnar Engine .
More from GitHub Advanced SecurityEvery GitHub Advanced Security release →
Security improvements for SSH
We’re removing several SSH algorithms, adding a new algorithm, and requiring larger RSA SSH keys to improve security. The changes are as follows: We’re removing the ability to use RSA keys using SHA-1 in SSH (i.e., the ssh-rsa signature type, including ssh-rsa-cert-v01@openssh.com certificates using SHA-1).
Deprecation notice: All-platform CodeQL bundle
Starting with CodeQL CLI 2.27.0 , the all-platform CodeQL bundle (i.e., codeql-bundle.tar.gz and codeql-bundle.tar.zst ), which includes the binaries for all supported platforms up to this release, is marked as deprecated. In mid-March 2027, we will remove the all-platform CodeQL bundle.
Manage the code coverage ruleset condition with the REST API
You can now use the generally available REST API to manage the Restrict code coverage repository ruleset option, in addition to the existing UI support. This ruleset lets you enforce a minimum code coverage percentage based on line coverage or set a maximum tolerable coverage drop for a pull request.
Stage-only npm tokens for safer automation
You can now select Read and write (stage only) when creating an npm granular access token. This lets your automated workflows stage package versions for review without giving the token permission to publish new versions directly to the npm registry. Your workflow uses npm stage publish to submit a version.
CodeQL 2.27.1 adds C and C++ query and Kotlin 2.4.20 support
CodeQL 2.27.1 adds new queries for C/C++ and C#, support for Kotlin 2.4.20, and query-accuracy improvements. CodeQL is the static analysis engine behind GitHub code scanning, which helps you find and remediate security issues in your code.
Code scanning AI Scan no longer requires CodeQL default setup
You can now use AI Scan for pull requests to find security vulnerabilities, even when CodeQL default setup isn’t enabled on a repository. Previously, AI Scan for pull requests only ran on repositories where CodeQL default setup was configured.
Enforce GitHub Advanced Security configurations
Enterprise administrators can now enforce GitHub Advanced Security configurations across their organizations. This prevents both organization and repository administrators from overriding settings defined at the enterprise level, helping security and compliance teams apply consistent policies across their enterprise.
Rate limits for private vulnerability reports
Open source maintainers are receiving more low-quality and automated vulnerability reports, which can bury the reports that matter. Rate limits cap how many new reports a single account can submit in a day, both to your repository and across GitHub. This helps protect you from bulk and automated submissions, while legitimate researchers can still reach you.