What I've Been Working On: February

Work

February was a very busy month, but we shipped Inngest TypeScript SDK v4! A lot of what I’d been building toward in January finally landed, and the back half of the month was all about getting it across the finish line and documenting everything. I also wrote and published an Inngest blog post, entitled Every App You’ve Built is an ETL Pipeline.

The v4 Release

The big stuff: I consolidated the execution engine down to V1 everywhere, defaulted to optimized parallelism, made checkpointing opt-out instead of opt-in, and cleaned up a bunch of API surface area — removing the step.invoke string argument, moving event triggers into the options object, and adding staticSchema for type-only event schemas. A lot of these changes sound small in isolation but together they make the SDK significantly leaner.

Checkpointing in particular was a saga. I shipped fixes for buffer flushing, added graceful fallback to async flow when checkpoint errors happen, and landed a server-side fix in inngest/inngest to propagate SaveStep errors through the checkpoint API. Shockingly, making durable execution the default means you really need to make sure it works.

Pull Requests

inngest/inngest-js

• Default to Optimized Parallelism
• refactor: remove step.invoke string argument
• Move Event Triggers into Options
• feat: AI package updates (open)
• refactor: use V1 execution engine everywhere
• Log deprecation warnings for streaming allow or force
• chore: remove v4 migration doc in favor of issue
• chore: fix outdated secrets link
• Merge main into v4
• feat: add staticSchema for type-only event schemas
• fix: flush checkpoint buffer
• fix: fallback to async flow on checkpoint error
• V4 merge
• main -> v4
• Make INNGEST_CONNECT_ISOLATE_EXECUTION opt-out
• Update Test Package & Human Readable Steps in ops (open)

inngest/inngest

• feat: add skip reason to cloud ui
• feat: reset die after parallelism ends
• fix: propagate SaveStep errors in checkpoint API

inngest/website

• TypeScript SDK v4 Docs
• docs: updates for new v4 stuff

inngest/monorepo

• feat: add skip reasons to cloud

I also wrote the v3 -> v4 Migration guide and reviewed 18+ PRs from teammates covering middleware migrations, logging overhauls, and SDK infrastructure changes.

Photos

Here’s what February looked like: