Releases Index
Inngest

Inngest

inngest.comDeveloper Tools
$npx @buildinternet/releases get inngest
Recently Shipped19 releases · updated Nov 16, 2026

Recently added step.subscribe to the executor, app sync history across the API, CLI, and MCP, and JSON querying in Insights.

Runs can now receive and read matching events while they run, via step.subscribe. Combined with app sync history, you can inspect what an app synced and when without leaving the API. Both are also available in the CLI and MCP.

  • step.subscribe lets a running function read events as they arrive.
  • Sync history through the v2 API, inngest api list-app-syncs, and the list_app_syncs / get_app_sync tools.

The dev server's SQL-backed Insights now stores JSON columns as JSON text, so ->> and json_* work against run data. For example, data->>'$.user.id' = 'u1' filters on a string field.

A sleep-ID collision fix changes behavior mid-deploy. Retrying the same sleep across old and new executor versions can enqueue two IDs and wake a run twice. Finish in-flight sleeps or pause those functions before upgrading to 1.53.

@inngest/ci renamed its GitHub events to github-ci/... with no alias. Existing GitHub webhooks need their transform replaced with the new githubWebhookTransform, or their event prefix changed to github-ci/. CI checks now open with the fact that matters and show pipeline progress live.

The Python SDK gained sandboxes, AI eval sessions, scores, experiments via group.experiment, and deferred functions via ctx.defer. Connect workers now finish a function after losing their lease instead of cancelling it. The JS SDK added sandbox command shims. The v2 pause/resume endpoints still require server 1.49 or later.

Sleep IDs no longer collide between runs; lake JSON gets JSON operators

This release3 featuresNew capabilities1 enhancementImprovements to existing features2 fixesBug fixesAI-tallied from the release notes
Inngest Server · v1.53.0

Scheduled sleeps no longer collide between runs that reuse an event key, and the lake stores JSON columns as JSON text so they support ->> and json_* operators. A new error column on runs and run_trace_spans changes the lake's baseline DDL in place.

Read more ↗

step.subscribe inboxes ship; inngest deploy builds and deploys apps

This release3 featuresNew capabilities4 fixesBug fixesAI-tallied from the release notes
Inngest Server · v1.52.0

Runs can now receive and read matching events while they run via step.subscribe, and a new inngest deploy command builds an app described in inngest.toml and deploys it to Inngest compute. App sync history is now readable through two new v2 API endpoints plus CLI and MCP equivalents, and run details no longer show the previous run's selected step after navigating between runs.

Read more ↗

Sandboxes, sessions, and deferred functions land

This release5 featuresNew capabilities3 enhancementsImprovements to existing features3 fixesBug fixesAI-tallied from the release notes
Python SDK · inngest@0.5.20

Adds experimental sandboxes via step.sandbox and client.sandboxes, plus deferred functions through ctx.defer, AI sessions for evals, scores, and group.experiment. Connect workers now finish the running function when they lose a lease instead of cancelling it, and Event objects built with a malformed top-level meta now raise.

Read more ↗

Function replays and resume now in v2 API, CLI, MCP

This release2 featuresNew capabilities3 fixesBug fixesAI-tallied from the release notes
Inngest Server · v1.49.0

Functions can be replayed by time range and status, and paused functions resumed, through the v2 API, the CLI, or MCP. Also fixes a trailing-slash bypass of event request limits and improves run paging with skipped runs included.

Read more ↗

Connect resumes requests across executor recovery; gRPC limits raised

This release1 featureNew capabilities5 fixesBug fixesAI-tallied from the release notes
Inngest Server · v1.48.0

Connect now accepts execution requests and replies above 4 MiB over internal gRPC and no longer retries transport message-size violations, and duplicate Connect execution after executor failure is fixed by resuming the original request lease or buffered response. Also fixes renewed worker capacity reservations that stayed at capacity after abandonment, preserves step invokes after the execution cap, and upgrades Next.js and Sharp in the UI for GHSA-2464-fhr4-w9xw.

Read more ↗

Function pause via API, CLI, MCP; includeOutput soft-deprecated

This release7 featuresNew capabilities4 enhancementsImprovements to existing features13 fixesBug fixesAI-tallied from the release notes
Inngest Server · v1.47.0

Functions can now be paused through the REST API, CLI, and MCP, and the includeOutput parameter is soft-deprecated in favor of include=output on REST v2 run-list endpoints. Fixed runs getting stuck as Running when step discovery enqueues fail transiently, preserved singleton runs on scheduling retries, and stopped Connect cleanup from dropping refreshed connections.

Read more ↗