v0.8.9

What's Changed

• Pull user field in EventPayload to be generic and not specify fields by @jpwilliams in #58
• fix: require not defined on landing page by @callingmedic911 in #56

New Contributors

• @callingmedic911 made their first contribution in #56

Full Changelog: v0.8.8...v0.8.9

v0.8.8

What's Changed

• Fix: Lack of event key should not throw upon instantiation by @jpwilliams in #57

Full Changelog: v0.8.7...v0.8.8

v0.8.7

What's Changed

• Allow customising the fetch implementation in an Inngest client by @jpwilliams in #54
• Use timeout instead of ttl when pushing waitForEvent timeout by @jpwilliams in #55

Full Changelog: v0.8.6...v0.8.7

v0.8.6

What's Changed

• Fix event key checking wrong var when picking up from environment by @jpwilliams in #53

Full Changelog: v0.8.5...v0.8.6

v0.8.5

What's Changed

• Add ability for inngest/remix import to handle SDK UI by @jpwilliams in #50

Full Changelog: v0.8.4...v0.8.5

v0.8.4

• Revert "Add proxy script npx inngest to go to npx inngest-cli@latest (#49)" 914b109

v0.8.3...v0.8.4

v0.8.3

What's Changed

• Read event key from env before throwing an error by @tonyhb in #47
• Dev server integration tests by @jpwilliams in #48
• Add proxy script npx inngest to go to npx inngest-cli@latest by @jpwilliams in #49

Full Changelog: v0.8.1...v0.8.3

v0.8.2

• Ensure that we load event keys from environment variables during initialization

v0.8.1

• When manually triggering a cron, send expected body and headers (#46) a092ab3
• Inherit secrets on release flows d6bac9c
• Remove ms from date strings, set MS to 0 when comparing dates (#44) 762a0a1
• 🪄 Steps (#34) e608f33
• Hide dev UI when deployed to production (#41) 8535350
• Test example functions and repos together on every PR (#37) 77f477b
• Use hash.js@^1.1.7 instead of sha.js@^2.4.11 to remove buffer requirement (#36) a7618ef

v0.7.0...v0.8.1

v0.8.0

v0.8.0: Steps

This release of the SDK adds step functions to your serverless event-driven code. Using the new tools, you can create steps, sleep, and coordinate between events in your regular serverless functions hosted on any platform. For example:

import { createStepFunction } from "inngest";

const logic = createStepFunction("My complex logic", "user/created", ({ event, tools }) => {
  const to = event.user.email;

  tools.run("Send welcome email", () => {
    // This step will run and retry independently of the rest of the code if it errors.
    email({ to, type: "welcome" });
  });

  tools.sleep("24h");

  tools.run("Send followup email", () => {
    email({ to, type: "followup" });
  });
});

Learn more in our patterns or docs!