inngest@3.52.0
Minor Changes
-
#1288
daf858f0Thanks @jpwilliams! - Add the ability to create Durable Endpoint Proxies, used to redirect to Inngest run results using a user's own domain.import { Inngest, step } from "inngest"; import { endpointAdapter } from "inngest/edge"; const inngest = new Inngest({ id: "bun-sync-example", endpointAdapter: endpointAdapter.withOptions({ asyncRedirectUrl: "/poll", }), }); const server = Bun.serve({ port: 3000, routes: { "/": inngest.endpoint(async (_req) => { const foo = await step.run("example/step", async () => { return "Hello from step!"; }); return new Response(`Step result: ${foo}`); }), // Proxy endpoint - fetches results from Inngest and decrypts if needed "/poll": inngest.endpointProxy(), }, }); console.log(`Listening on ${server.hostname}:${server.port}`);
-
#1284
5717c64bThanks @jpwilliams! - Add a Durable Endpoints Next.js Adapter// app/api/my-endpoint/route.ts import { Inngest, step } from "inngest"; import { endpointAdapter } from "inngest/next"; const inngest = new Inngest({ id: "my-app", endpointAdapter, }); export const GET = inngest.endpoint(async (req) => { const foo = await step.run("my-step", () => ({ foo: "bar" })); return new Response(`Result: ${JSON.stringify(foo)}`); });
Patch Changes
-
#1297
32b59507Thanks @ptts! - FixextendProvider()failing to extend existing OTel providers by unwrapping theProxyTracerProviderreturned bytrace.getTracerProvider(). Previously, the proxy wrapper hid the underlying provider'saddSpanProcessormethod, causing"auto"mode to fall through tocreateProvider()and register duplicate instrumentations. -
#1292
9c8f5d94Thanks @jpwilliams! - Fix Durable Endpoints not capturing and obeying step plan forcing, resulting in strange behaviour during parallel flows -
#1285
9a7b0528Thanks @jpwilliams! - Handle checkpointing failures more gracefully across async checkpointing and Durable Endpoints