Skip to content
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

Proposal: Avoid using toSorted for compatibility with NodeJS 18 #210

Merged
merged 1 commit into from
Nov 7, 2024

Conversation

Machinarius
Copy link
Contributor

Should fix #209

@CahidArda
Copy link
Contributor

tests aren't passing because it seems like they can't access the env keys. but I ran the workflow tests locally and they are fine. will merge

Thanks for the contribution @Machinarius!

I will make sure to update the workflow-js this way too.

@CahidArda CahidArda merged commit 013a3ab into upstash:main Nov 7, 2024
4 of 6 checks passed
@Machinarius
Copy link
Contributor Author

@CahidArda Thank you! We will upgrade to the stand-alone Workflow SDK as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Using toSorted is needlessly bumping the NodeJS requirement to v20+
2 participants