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

Add Node 17 compatibility #7708

Closed
3 tasks done
mtrezza opened this issue Nov 18, 2021 · 2 comments · Fixed by #7896
Closed
3 tasks done

Add Node 17 compatibility #7708

mtrezza opened this issue Nov 18, 2021 · 2 comments · Fixed by #7896
Labels
bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature

Comments

@mtrezza
Copy link
Member

mtrezza commented Nov 18, 2021

New Feature / Enhancement Checklist

Current Limitation

Parse Server does not have a CI job with Node 17.

Feature / Enhancement Description

Add Node 17 CI job (similar to the currently existing Node 14 CI job) and make it pass.

Example Use Case

n/a

Alternatives / Workarounds

n/a

@parse-github-assistant
Copy link

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

@mtrezza mtrezza added bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) type:improvement labels Nov 18, 2021
@mtrezza mtrezza added type:feature New feature or improvement of existing feature and removed type:improvement labels Dec 6, 2021
@mtrezza mtrezza linked a pull request Mar 27, 2022 that will close this issue
4 tasks
@mtrezza mtrezza pinned this issue Mar 28, 2022
@mtrezza
Copy link
Member Author

mtrezza commented Mar 28, 2022

The PR is currently stuck due to 2 failing GraphQL tests, see #7896 (comment); if anyone wants to take a look please do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant