GitHub Enterprise adds credential inventory exports

UpdateSep 21, 2026VerifiedAdded Sep 22, 2026

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).

Security Pricing Observability Developer tools

Read GitHub's release notes

https://github.blog/changelog/2026-09-21-github-enterprise-adds-credential-inventory-exports

Summaries of vendors' own notes. Product names and logos belong to their owners; logos via logo.dev.

More GitHub Advanced Security releases

GitHub Advanced SecuritySep 22, 2026

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).

UpdateSecurityRegionsSource

GitHub Advanced SecuritySep 22, 2026

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.

DeprecationObservabilityDeveloper toolsSource

GitHub Advanced SecuritySep 18, 2026

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.

GAObservabilityDeveloper toolsSource

GitHub Advanced SecuritySep 18, 2026

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.

UpdateGovernanceSecurityDeveloper toolsSource

GitHub Advanced SecuritySep 16, 2026

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.

PreviewSecurityObservabilitySource

GitHub Advanced SecuritySep 15, 2026

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.

UpdateGovernanceSecurityObservabilitySource

GitHub Advanced SecuritySep 10, 2026

AI Scan for pull request APIs in public preview

You can now manage GitHub code scanning’s AI Scan for pull request enablement with REST API endpoints at the organization and repository levels. This public preview gives teams a programmatic way to roll out AI-powered security detections for pull requests across select repositories without manually configuring each setting in the GitHub UI.

PreviewSecurityObservabilityDeveloper toolsSource

GitHub Advanced SecuritySep 9, 2026

npm extends recovery-code security holds to all accounts

npm now places a temporary 72-hour security hold on any account after a successful recovery-code sign-in, extending a protection that previously applied only to high-impact accounts. This change applies to all npm accounts. During the hold, publishing and other security-sensitive writes, including creating access tokens, are paused.

UpdateSecurityObservabilitySource

Also shipped on Sep 21, 2026

Google Cloud BigQuerySep 21, 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.

GASQLSource

Databricks Databricks Data Intelligence PlatformSep 21, 2026

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 .

GASQLObservabilityDeveloper toolsSource

Snowflake Snowflake Cortex AISep 21, 2026

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.

PreviewSQLPricingSource

Snowflake Snowflake Cortex AISep 21, 2026

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.

PreviewPricingSource

Snowflake Snowflake Cortex AISep 21, 2026

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.

PreviewAI agentsDeveloper toolsSource

Google Cloud AlloyDBSep 21, 2026

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 .

GAVector searchPerformanceSource