feat: remove Node 12 support #2277
Merged
Conversation
This file contains 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
Thanks for opening this pull request!
|
damianstasik
force-pushed
the
remove-node12-support
branch
from
2fd1f15 to
b910845
Compare
damianstasik
changed the title
damianstasik
force-pushed
the
remove-node12-support
branch
from
b910845 to
87c090f
Compare
5 tasks
|
Not sure we can merge this before end of the year, since Parse Server still supports Node 12, therefore dashboard should probably too. We'll remove Node 12 support in Parse Server on Jan 1st. Which PRs are blocked because of Node 12 support? |
mtrezza
approved these changes
Sep 27, 2022
There was a problem hiding this comment.
I think we can merge this; this needs to be merged as a breaking change.
Parse Server is the principal package, so as a rule we should keep Parse Dashboard aligned regarding its Node version requirements. However, it's great to see that you found some time to work on modernizing Parse Dashboard and pick up the other PRs. I wound't want to see your efforts being blocked by this PR - and in 3 months Parse Server will drop Node 12 support anyway.
mtrezza
changed the title
|
🎉 This change has been released in version 5.0.0-alpha.1 |
Closed
3 tasks
parseplatformorg
pushed a commit
that referenced
this pull request
Oct 17, 2022
# [5.0.0-beta.1](4.2.0...5.0.0-beta.1) (2022-10-17) ### Bug Fixes * increase required Node engine version to `>=14.20.1`; this is a breaking change, but will be published as a patch version because the change should have been done with the release of `5.0.0-alpha.1` which has just been released ([#2281](#2281)) ([50de52b](50de52b)) * minor UI layout issues ([#2270](#2270)) ([51d083b](51d083b)) * raw value of read-only date field in data browser cannot be copied ([#2326](#2326)) ([4af7b98](4af7b98)) * using browser navigation backward / forward button clears data browser ([#2317](#2317)) ([7d9b957](7d9b957)) ### Features * improve distinction between deletion confirmation dialogs ([#2319](#2319)) ([23c12ff](23c12ff)) * keep entered filter value when changing filter operator ([#2313](#2313)) ([d6d38bf](d6d38bf)) * remove Node 12 support ([#2277](#2277)) ([18b0e76](18b0e76)) ### BREAKING CHANGES * This version removes support for Node 12; the new minimum required Node version is 14. ([18b0e76](18b0e76))
|
🎉 This change has been released in version 5.0.0-beta.1 |
parseplatformorg
pushed a commit
that referenced
this pull request
Nov 1, 2022
# [5.0.0](4.2.0...5.0.0) (2022-11-01) ### Bug Fixes * increase required Node engine version to `>=14.20.1`; this is a breaking change, but will be published as a patch version because the change should have been done with the release of `5.0.0-alpha.1` which has just been released ([#2281](#2281)) ([50de52b](50de52b)) * minor UI layout issues ([#2270](#2270)) ([51d083b](51d083b)) * raw value of read-only date field in data browser cannot be copied ([#2326](#2326)) ([4af7b98](4af7b98)) * using browser navigation backward / forward button clears data browser ([#2317](#2317)) ([7d9b957](7d9b957)) ### Features * improve distinction between deletion confirmation dialogs ([#2319](#2319)) ([23c12ff](23c12ff)) * keep entered filter value when changing filter operator ([#2313](#2313)) ([d6d38bf](d6d38bf)) * remove Node 12 support ([#2277](#2277)) ([18b0e76](18b0e76)) ### BREAKING CHANGES * This version removes support for Node 12; the new minimum required Node version is 14. ([18b0e76](18b0e76))
|
🎉 This change has been released in version 5.0.0 |
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.
New Pull Request Checklist
Issue Description
This PR removes Node.js 12 support.
Related issue: #2190
Approach
TODOs before merging