Skip to content

Remove Node 12 support #2190

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

Closed
3 tasks done
mtrezza opened this issue Jun 28, 2022 · 3 comments · Fixed by #2277
Closed
3 tasks done

Remove Node 12 support #2190

mtrezza opened this issue Jun 28, 2022 · 3 comments · Fixed by #2277
Labels
type:feature New feature or improvement of existing feature

Comments

@mtrezza
Copy link
Member

mtrezza commented Jun 28, 2022

New Feature / Enhancement Checklist

Current Limitation

Node 12 it out of LTS, but still tested in CI and range in node engine

Feature / Enhancement Description

Remove node 12 support

Removing Parse Server compatibility would be a breaking change, so this can only be done in Parse Server 6.

Example Use Case

n/a

Alternatives / Workarounds

n/a

@parse-github-assistant
Copy link

parse-github-assistant bot commented Jun 28, 2022

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

@mtrezza mtrezza added the type:feature New feature or improvement of existing feature label Jun 28, 2022
@mtrezza
Copy link
Member Author

mtrezza commented Aug 5, 2022

Dependency PRs already begin to require Node 14, such as #2228. They can't be merged until we drop Node 12 support.

@mtrezza mtrezza pinned this issue Aug 5, 2022
@mtrezza mtrezza unpinned this issue Sep 12, 2022
@mtrezza
Copy link
Member Author

mtrezza commented Sep 27, 2022

Closed via #2277

@mtrezza mtrezza closed this as completed Sep 27, 2022
@mtrezza mtrezza linked a pull request Sep 27, 2022 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature New feature or improvement of existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant