---
name: Inngest Changelog
slug: inngest-changelog
type: scrape
source_url: https://www.inngest.com/changelog
organization: Inngest
organization_slug: inngest
total_releases: 10
latest_version: v4
latest_date: 2026-03-25
last_updated: 2026-04-15
tracking_since: 2025-10-03
canonical: https://releases.sh/inngest/inngest-changelog
organization_url: https://releases.sh/inngest
---

<Summary type="rolling" window-days="90" release-count="7">
The TypeScript SDK v4 reshaped the foundation with rewritten middleware, Standard Schema support, and parallel step optimization enabled by default—a major version with breaking changes, though migration is typically straightforward. Realtime graduated to first-class status in the SDK itself, consolidating channels and subscriptions into improved APIs that replaced the legacy `@inngest/realtime` package. Beyond the SDK, durability expanded beyond workflows into API handlers via Durable Endpoints, agent skills shipped for Claude Code and Cursor, and the dashboard gained timeline visualization with step-level timing details for debugging long-running functions.
</Summary>

<Summary type="monthly" period="March 2026" release-count="3">
Realtime graduated to first-class status in the TypeScript SDK with improved developer experience across channels, topics, and subscribing, deprecating the separate `@inngest/realtime` package. TypeScript SDK v4 entered beta with rewritten middleware, Standard Schema support for event validation, parallel step execution enabled by default, and structured logging, alongside traces UI enhancements that added timeline zooming and response header inspection for long-running functions.
</Summary>

<Summary type="monthly" period="February 2026" release-count="3">
Inngest shipped several expansions to its platform in February 2026, moving beyond workflow-specific durability into broader development patterns. The release of Durable Endpoints brought the framework's retry, recovery, and observability capabilities into standard API handlers through a new `inngest.endpoint()` wrapper and `step.run()` primitives, launching in public beta for Next.js and Bun. Simultaneously, Inngest Agent Skills emerged as a set of pre-built capabilities for AI coding agents like Claude Code, Cursor, and Windsurf, covering project configuration, event design, durable functions, workflow composition, flow control, and middleware to streamline AI-assisted development within Inngest. On the infrastructure side, the team published an official Helm chart as an OCI artifact in v0.3.0, simplifying self-hosted deployments while incorporating Kubernetes best practices through improved labels support and enhanced probes.
</Summary>

<Release version="v4" date="March 25, 2026" published="2026-03-25T00:00:00.000Z" url="https://www.inngest.com/changelog#v4">
## First-class realtime support with improved DX in the TypeScript SDK

Realtime is now a first-class part of the TypeScript SDK. Channels, topics, publishing, and subscribing all have an improved DX, along with an updated `useRealtime` React hook. The legacy `@inngest/realtime` package is deprecated in favor of the built-in realtime APIs in `inngest`, `inngest/realtime`, and `inngest/react`.
</Release>

<Release date="March 13, 2026" published="2026-03-13T00:00:00.000Z" url="https://www.inngest.com/changelog#traces-ui-improvements">
## Traces UI improvements

Added timeline header with time brush for zooming into specific time ranges in traces for long-running functions. Improved step details panel with timing info, step-specific fields, and a new Headers tab showing response headers returned by SDK endpoints.
</Release>

<Release date="March 4, 2026" published="2026-03-04T00:00:00.000Z" url="https://www.inngest.com/changelog#typescript-sdk-v4">
## TypeScript SDK v4

The TypeScript SDK v4 is now available in beta! Major improvements include:

* **Rewritten middleware** — Hooks are more intuitive, less overloaded, and enable new use cases.
* **Better schemas** — Runtime event data validation with [Standard Schema](https://standardschema.dev/?ref=inngest) support (not just Zod!).
* **Faster by default** — Parallel step optimization and checkpointing are both enabled by default, leading to fewer requests and lower latency.
* **Improved logging** — Structured logging (Pino-style) and cleaner separation of internal vs. app logs.
* **Cleaner API** — Triggers in the options object, lazy init for edge runtimes, and more compile-time safety

This is a major version with breaking changes, but for most apps the migration is trivial.

Install the beta with `npm install inngest@beta`.

More info:
* [Announcement blog post](https://www.inngest.com/changelog/blog/typescript-sdk-v4.0?ref=changelog-typescript-sdk-v4)
* [Migration guide](https://www.inngest.com/changelog/docs/reference/typescript/v4/migrations/v3-to-v4?ref=changelog-typescript-sdk-v4)
</Release>

<Release version="v0.3.0" date="February 18, 2026" published="2026-02-18T00:00:00.000Z" url="https://www.inngest.com/changelog#v0-3-0">
## Helm chart v0.3.0

Official Helm chart now published as OCI artifact for easy installation and upgrades for self-hosting Inngest. Includes improved labels support with Kubernetes best practices and improved probes.
</Release>

<Release date="February 18, 2026" published="2026-02-18T00:00:00.000Z" url="https://www.inngest.com/changelog#agent-skills-for-coding-agents">
## Agent Skills for coding agents

Released Inngest Agent Skills — pre-built skills for AI coding agents (Claude Code, Cursor, Windsurf) covering project configuration, event design, durable functions, workflow composition, flow control, and middleware. Six skills available with full Inngest development workflow coverage.
</Release>

<Release date="February 10, 2026" published="2026-02-10T00:00:00.000Z" url="https://www.inngest.com/changelog#durable-endpoints-durability-beyond-workflows">
## Durable Endpoints: Durability beyond workflows

Durable Endpoints bring Inngest's durability into API handlers. Wrap endpoint code with `inngest.endpoint()` and use `step.run()` for automatic retries, recovery, and observability. Features zero configuration, automatic recovery from last successful step, built-in observability, and low latency powered by Checkpointing. Available in public beta for Next.js and Bun.
</Release>

<Release date="January 19, 2026" published="2026-01-19T00:00:00.000Z" url="https://www.inngest.com/changelog#docs-markdown-actions-for-llms">
## Docs markdown actions for LLMs

Docs now have quick actions to copy or open pages in Markdown format and open conversations with markdown URLs in Claude, ChatGPT, or other LLM providers. The llms.txt file includes markdown URLs for each page to reduce required context.
</Release>

<Release date="December 10, 2025" published="2025-12-10T00:00:00.000Z" url="https://www.inngest.com/changelog#checkpointing-near-zero-latency-for-durable-workflows">
## Checkpointing: Near-zero latency for durable workflows

Released developer preview of Checkpointing, enabling near-zero inter-step latency in durable workflows. Dogfooding results show 50% reduction in workflow duration and near-zero inter-step latency. Available as opt-in configuration at client or function level.
</Release>

<Release date="October 27, 2025" published="2025-10-27T00:00:00.000Z" url="https://www.inngest.com/changelog#dev-server-mcp">
## Dev Server MCP

Released MCP Integration for the Inngest dev server, enabling AI-assisted development workflows. Connect Claude Code, Cursor, and other AI assistants directly to local Inngest functions. Provides 8 tools: event management, real-time monitoring, direct function invocation, documentation access, and integration testing.
</Release>

<Release date="October 3, 2025" published="2025-10-03T00:00:00.000Z" url="https://www.inngest.com/changelog#new-webhook-content-types">
## New webhook content types

Webhooks are now more flexible with the addition of `x-www-form-urlencoded` and `multipart/form-data` content types. When sending a request with either of these content types, your webhook transform will have access to both a JSON object representation of the body and the raw body as a string.

Example: When sending form-encoded data like `name=Alice&messages=hello&messages=world`, the webhook transform receives both the parsed JSON object and the raw body string.
</Release>