v0.2.0

What's Changed

Features:

• Update client.cancel to allow canceling with url and cancelling all by @CahidArda in #26
• context.cancel to cancel the current workflow by @CahidArda in #8

Fixes:

• Update failureFunction args by @fahreddinozcan in #27
• Update timeout parameter in waitForEvent by @joschan21 in #23
• Rename errors by @CahidArda in #8
• Lazy fetch feature to allow longer and larger workflows by @CahidArda in #8
• Handle network caused errors by @CahidArda in #16
• Check custom auth in failureFunction by @CahidArda in #28

Migration from 0.1.x to 0.2.0

If you were using the workflow client to cancel workflows by id, you should update it like:

import { Client } from "@upstash/workflow";
const client = new Client(...)
client.cancel({
- workflowRunId: "runId"
+ ids: "runId"
})

context.waitForEvent should be updated like:

await context.waitForEvent(
  "wait step",
  "eventId"
- "10s"
+ { timeout: "10s" }
)

failureFunction parameters should be updated as an object:

failureFunction: async (
-  context, failStatus, failResponse, failHeaders
+  { context, failStatus, failResponse, failHeaders }
) => { ... }

If you were importing and using the errors QStashWorkflowError or QStashWorkflowAbort, they are now renamed as WorkflowError and WorkflowAbort.

New Contributors

• @joschan21 made their first contribution in #23

Full Changelog: v0.1.5...v0.2.0

0.1.5-cf-canary

Canary for fixing loop detection issue in cloudflare

Full Changelog: v0.1.5...0.1.5-cf-canary

v0.1.5

What's Changed

• generate random workflow id with math.random by @CahidArda in #25

Full Changelog: v0.1.4...v0.1.5

v0.1.4

Fix failure function headers which caused an issue when context.call was used.

Full Changelog: v0.1.3...v0.1.4

v0.1.3

What's Changed

Features:

• Allow string duration such as 1d or 30s in context.sleep & context.waitForEvent by @fahreddinozcan in #12
• Integrations for Astro and Express by @fahreddinozcan in #13 and #14
• Add client.trigger to make it possible to start workflows and get the workflow run id by @CahidArda in #18
• Add context.call retry option by @CahidArda in #19
• Add CI tests by @CahidArda in #21

Fixes:

• Sort steps with .sort instead of .toSorted to allow Node18 by @CahidArda in #17
• Add bootstrap script and fix examples by @CahidArda in #15

New Contributors

• @fahreddinozcan made their first contribution in #12

Full Changelog: v0.1.2...v0.1.3

v0.1.3-crpyto-canary-2

Canary for #20

Full Changelog: v0.1.3-crpyto-canary...v0.1.3-crpyto-canary-2

v0.1.3-crpyto-canary

Canary for #20

Full Changelog: v0.1.2...v0.1.3-crpyto-canary

v0.1.2-omit-errors

Canary for #16.

Full Changelog: v0.1.2...v0.1.2-omit-errors

v0.1.2-canary-astro

Canary for #11

Full Changelog: v0.1.2...v0.1.2-canary-astro

v0.1.2

What's Changed

Fixed the base64 eventData issue. Now eventData is decoded by default.

• Stringify/parse step.out by @CahidArda in #5

Workflow will now stringify and parse all step results. We are planning to make it possible to write your own serializer/deserializer in the future.

• Fix Protocol and Feature Headers in context.call by @CahidArda in #6

Addressed two issues in context.call:

• calling another workflow endpoint would result in an error
• feature set header was sent incorrectly. resulting in workflows which failed but stayed in RUN_STARTED state.

Full Changelog: v0.1.1...v0.1.2