-
Notifications
You must be signed in to change notification settings - Fork 22
DX-2357: Workflow Region Migration #166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
CahidArda
wants to merge
15
commits into
main
Choose a base branch
from
DX-2357-wf-migration
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* fix: rm context.agents * fix: rm agents example * fix: rm agents-instagram-post-generator example * fix: rm agents-researcher * fix: rm ai sdk dependencies * fix: rm unnecessary dependencies and make zod peer dependency * feat: rm keepTriggerConfig option and make it true by default in trigger * fix: rm useFailureFunction option and allow failure callback without failure function in serve * fix: remove cross reference exmaple from ci and fix ai sdk route example * fix: cast headers to Headers type in Client class
* feat: add middleware * feat: add name and workflowRunId params * feat: replace logger with middleware * fix: improve logger and add verbose option * fix: fmt * fix: tests * fix: rm workflowRunId from init and runMiddlewares params instead, we assign workflowRunId at the start of the endpoint * feat: add context to middleware lifecycle event payload * fix: change local warn to info and clean loggingMiddleware * fix: info message * fix: add back handle third party * fix: add back handleThirdPartyCallResult tests * fix: add middleware to ci * fix: add back tests, rm unused file and params * fix: rm flaky parallel wf * fix: update docstrings * fix: rm flaky tests
* fix: seperate error classes and rm simple finish reason * fix: rm internal errors from exports * fix: throw if stepName !== string and fix failure function state type * fix: fmt * Update src/workflow-requests.ts Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* feat: rm serve options retries, failureUrl, retryDelay, flowControl are removed. Users should configure these values in client.trigger. Once they are passed in client.trigger, they will apply across the worklfow. * fix: ci endpoints * fix: rm retries from parameters * fix: bump expected version * fix: rm retries * fix: ci tests * fix: call count * fix: rm old docstrings
* fix: rm stringifyBody parameter * fix: fmt * fix: build errors * fix: ci tests * fix: make serve-many tests more explicit * fix: expected call count
… condition tests (#162) * feat: rm public onStepFinish option and simplify serve option types * fix: handle failure-callback-undefined case correctly and add tests
* feat: add unknown sdk feature when user uses QStash /trigger endpoint, QStash will send a request with a new header named Upstash-Workflow-Unknown-Sdk. if this is received, SDK should read the workflow run id from the headers, initial payload from the step list (initialy payload isn't sent as it is. it's inside the usual step list), and publish a new trigger request. QStash will read the feature set and protocol versions from this request and start the workflow as usual, without the unknown SDK header this time. * fix: change version to 1.0.0 * fix: add non-retryable error to ci tests * fix: add Upstash-workflow-sdk to response headers and add tests for /trigger endpoint * fix: fmt * fix: tests * fix: add qstash url default * fix: typo * fix: express build errors * fix: handle lazyFetch in /trigger * fix: ci test and fmt * fix: pin @types/express-serve-static-core version and bump express * fix: express v5 parameter name error expressjs/express#6428 (comment)
7911861 to
2eb47bd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Will be merged after #165. So we use that PR as target branch.