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

feat: Add support for Node 20, remove support for Node 14 and 16 #2063

Merged
merged 7 commits into from
Mar 9, 2024
Merged

feat: Add support for Node 20, remove support for Node 14 and 16 #2063

merged 7 commits into from
Mar 9, 2024

Conversation

nikeee
Copy link
Contributor

@nikeee nikeee commented Dec 5, 2023

According to the readme, parse follows the supported node versions:

Parse JS SDK is continuously tested with the most recent releases of Node.js to ensure compatibility.
We follow the Node.js Long Term Support plan and only
test against versions that are officially supported and have not reached their end-of-life date.

This commit aligns the repository with the currently supported Node.js versions.
See:
https://github.com/nodejs/Release

Closes: #2065

According to the readme, parse follows the supported node versions:

> Parse JS SDK is continuously tested with the most recent releases of Node.js to ensure compatibility.
> We follow the [Node.js Long Term Support plan](https://github.com/nodejs/Release) and only
> test against versions that are officially supported and have not reached their end-of-life date.

This commit aligns the repository with the currently supported Node.js versions
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title fix: align currently supported node versions fix: Align currently supported node versions Dec 5, 2023
Copy link

parse-github-assistant bot commented Dec 5, 2023

Thanks for opening this pull request!

Copy link

@jordiyapz jordiyapz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's good enough.

Copy link
Member

@mtrezza mtrezza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The supported Node versions of Parse Server 7 will be only Node 18 and 20; could you change this in this PR also to Node 18 and 20 only?

Copy link

codecov bot commented Feb 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (556312d) to head (6f5e3fc).

Additional details and impacted files
@@            Coverage Diff            @@
##             alpha     #2063   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           61        61           
  Lines         6173      6173           
  Branches      1494      1494           
=========================================
  Hits          6173      6173           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@mtrezza mtrezza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@mtrezza mtrezza changed the title fix: Align currently supported node versions feat: Add support for Node 20; remove support for Node 14, 16 Mar 9, 2024
@mtrezza mtrezza changed the title feat: Add support for Node 20; remove support for Node 14, 16 feat: Add support for Node 20; remove support for Node 14 and 16 Mar 9, 2024
@mtrezza mtrezza changed the title feat: Add support for Node 20; remove support for Node 14 and 16 feat: Add support for Node 20, remove support for Node 14 and 16 Mar 9, 2024
@mtrezza mtrezza merged commit 74eb4d5 into parse-community:alpha Mar 9, 2024
9 checks passed
parseplatformorg pushed a commit that referenced this pull request Mar 9, 2024
# [5.0.0-alpha.1](4.3.1-alpha.2...5.0.0-alpha.1) (2024-03-09)

### Features

* Add support for Node 20, remove support for Node 14 and 16 ([#2063](#2063)) ([74eb4d5](74eb4d5))

### BREAKING CHANGES

* Removes support for Node 14 and 16. ([74eb4d5](74eb4d5))
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 5.0.0-alpha.1

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label Mar 9, 2024
parseplatformorg pushed a commit that referenced this pull request Mar 17, 2024
# [5.0.0-beta.1](4.3.1...5.0.0-beta.1) (2024-03-17)

### Bug Fixes

* Calling `Parse.Object.relation.add` multiple times adds only the first object ([#2078](#2078)) ([0f98117](0f98117))

### Features

* Add comment to MongoDB query via `Parse.Query.comment` ([#2088](#2088)) ([a970913](a970913))
* Add compatibility with Parse Server 7 ([#2089](#2089)) ([86600bc](86600bc))
* Add support for Node 20, remove support for Node 14 and 16 ([#2063](#2063)) ([74eb4d5](74eb4d5))

### BREAKING CHANGES

* Parse JS SDK 5 requires Parse Server 7 and is incompatible with Parse Server 6. ([86600bc](86600bc))
* Removes support for Node 14 and 16. ([74eb4d5](74eb4d5))
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 5.0.0-beta.1

@parseplatformorg parseplatformorg added the state:released-beta Released as beta version label Mar 17, 2024
parseplatformorg pushed a commit that referenced this pull request Mar 17, 2024
# [5.0.0](4.3.1...5.0.0) (2024-03-17)

### Bug Fixes

* Calling `Parse.Object.relation.add` multiple times adds only the first object ([#2078](#2078)) ([0f98117](0f98117))

### Features

* Add comment to MongoDB query via `Parse.Query.comment` ([#2088](#2088)) ([a970913](a970913))
* Add compatibility with Parse Server 7 ([#2089](#2089)) ([86600bc](86600bc))
* Add support for Node 20, remove support for Node 14 and 16 ([#2063](#2063)) ([74eb4d5](74eb4d5))

### BREAKING CHANGES

* Parse JS SDK 5 requires Parse Server 7 and is incompatible with Parse Server 6. ([86600bc](86600bc))
* Removes support for Node 14 and 16. ([74eb4d5](74eb4d5))
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 5.0.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label Mar 17, 2024
@nikeee nikeee deleted the support/upgrade-node-versions branch March 17, 2024 02:57
mtrezza added a commit to mtrezza/Parse-SDK-JS that referenced this pull request Mar 23, 2024
…rification

* alpha:
  chore(release): 5.0.0-beta.1 [skip ci]
  chore(release): 5.0.0-alpha.3 [skip ci]
  feat: Add comment to MongoDB query via `Parse.Query.comment` (parse-community#2088)
  chore(release): 5.0.0-alpha.2 [skip ci]
  feat: Add compatibility with Parse Server 7 (parse-community#2089)
  chore(release): 5.0.0-alpha.1 [skip ci]
  feat: Add support for Node 20, remove support for Node 14 and 16 (parse-community#2063)
  refactor: Upgrade ws from 8.15.1 to 8.16.0 (parse-community#2087)
  ci: Remove manual caching for `actions/setup-node` (parse-community#2064)
  chore(release): 4.3.1-alpha.2 [skip ci]
  fix: Calling `Parse.Object.relation.add` multiple times adds only the first object (parse-community#2078)
  refactor: Upgrade ws from 8.15.0 to 8.15.1 (parse-community#2074)
  chore(release): 4.3.1 [skip ci]
  release
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:released Released as stable version state:released-alpha Released as alpha version state:released-beta Released as beta version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Align currently supported Node.js version
4 participants