-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Open
Labels
state:breakingBreaking change requires major version increment and `BREAKING CHANGE` commit messageBreaking change requires major version increment and `BREAKING CHANGE` commit messagetype:featureNew feature or improvement of existing featureNew feature or improvement of existing feature
Description
New Feature / Enhancement Checklist
- Report security issues confidentially.
- Any contribution is under this license.
- Before posting search existing issues.
Feature / Enhancement Description
Task list for release of Parse Server 9.
Tasks
Common
- Freeze current LTS branch
release-#.x.xin GitHub repo settings - Publish final releases on
beta(currently not in use) andreleasebranches - Ensure all branches
alpha,beta(currently not in use),releaseare on latest commit - Add new LTS branch
release-#.x.x - Create GitHub repository branch rules for new LTS branch
release-#.x.x - Update Snyk branches to monitor
- Remove monitoring old LTS branch, add new LTS branch
- Update .releaserc.js for new LTS branch (preparatory step for when the new to-be-released major version will become the LTS version on the
release.#.x.xbranch in the future) - Remove support for Node versions that have reached their EOL
- Remove Node versions from CI in
ci.yml - Specify the exact node version in package-lock
engines.node, not just the major version, and use latest Node version, e.g. instead of>=18 <19 || >=20 <21use>=18.2.3 <19 || >=20.2.3 <21 - Remove tests that target only removed Node versions
- Ensure upgraded dependencies (push adapter, Parse JS SDK, etc.) don't require higher min Node version; check the unmerged PRs of all dependencies for the CI job "Node Engine Check" to determine the minimum required Node version of parse-server to satisfy all dependencies; merge the min Node version increment PR first, then the PRs of dependencies, so they are merged with green CI
- feat: Increase required minimum Node version to
20.19.0#9970
- Remove Node versions from CI in
- Remove support for MongoDB versions that have reached their EOL
- Remove MongoDB versions from CI in
ci.yml - Update MongoDB versions in scripts in
package.json - Remove tests that target only removed MongoDB versions
- feat: Increase required minimum MongoDB version to
7.0.16#9971
- Remove MongoDB versions from CI in
- Remove support for Postgres versions that have reached their EOL
- Remove Postgres versions from CI in
ci.yml - Remove tests that target only removed Postgres versions
- feat: Increase required minimum version to Postgres
16, PostGIS3.5#9972
- Remove Postgres versions from CI in
- Remove deprecated Parse Server options
- Merge latest dependencies
- Merge any other breaking changes that have been held-off for a major release
Nice-to-have features (no release blocker)
- feat: Add Parse Server options
maxIncludeQueryComplexity,maxGraphQLQueryComplexityto limit query complexity for performance protection #9920 (comment) - Set default values for max depth and max fields #9928
Excluded from this release (with explanation)
- refactor: Bump graphql-upload from 15.0.2 to 17.0.0 #9342 (can be merged after removing Node 22 support from Parse Server)
Notes
- Releases on the LTS branch will fail until the next stable release on the
releasebranch due to a bug in semantic release, see EINVALIDNEXTVERSION error when releasing a patch from maintenance branch semantic-release/semantic-release#1487 (comment). Once the major Parse Server version has been released, the LTS release should be triggered again manually by making a non-release commit, e.g. of typeciorrefactor.
Metadata
Metadata
Assignees
Labels
state:breakingBreaking change requires major version increment and `BREAKING CHANGE` commit messageBreaking change requires major version increment and `BREAKING CHANGE` commit messagetype:featureNew feature or improvement of existing featureNew feature or improvement of existing feature