Data and AI releases

548 this month · 176 companies

Logs - Logpush subrequest merging for HTTP requests

UpdateNot yet verified

When a Cloudflare Worker intercepts a visitor request, it can dispatch additional outbound fetch calls called subrequests. By default, each subrequest generates its own log entry in Logpush, resulting in multiple log lines per visitor request.

Observability

Also shipped Apr 21, 2026Cloudflare in April 2026 →

Meet Replit Security Agent

Replit Security Agent performs comprehensive security reviews of codebases using a hybrid approach with Semgrep and HoundDog.ai. It automates threat modeling and vulnerability identification before projects are published.

GA
Source ↗

LlamaIndex 0.14.21

Release Notes [2026-04-21] llama-index-callbacks-honeyhive [0.5.0] chore(deps): bump the pip group across 87 directories with 2 updates ( #21382 ) chore(deps): bump the pip group across 68 directories with 2 updates ( #21394 ) llama-index-core [0.14.21] fix(core): prevent KeyError in DocumentSummaryIndex.delete_nodes when invalid node ID is provided (...

Update
Source ↗

More from Cloudflare developer platformEvery Cloudflare developer platform release →

Cloudflare Fundamentals - Network Overview page in the dashboard

A new Network Overview page in the Cloudflare dashboard gives you a single starting point for network security and connectivity products. From the Network Overview page, you can: Connect resources with Cloudflare Tunnel - Create tunnels to connect your infrastructure to Cloudflare without exposing it to the public Internet.

Update
Source ↗

WAF Release - 2026-04-21

This week's release introduces a new detection for a Remote Code Execution (RCE) vulnerability in Apache ActiveMQ (CVE-2026-34197) and an updated signature for Magento 2 - Unrestricted File Upload. Alongside these detections, we are continuing our work on rule refinements to provide deeper security insights for our customers.

Update
Source ↗

Workers - WebSocket binary messages now delivered as Blob by default

Binary frames received on a WebSocket are now delivered to the message event as Blob ↗ objects by default. This matches the WebSocket specification ↗ and standard browser behavior. Previously, binary frames were always delivered as ArrayBuffer ↗ . The binaryType property on WebSocket controls the delivery type on a per-WebSocket basis.

Update
Source ↗