Repository navigation
Prepare release of Parse Server 8 #9366
Description
New Issue Checklist
- Report security issues confidentially.
- Any contribution is under this license.
- Before posting search existing issues.
Issue Description
Task list for release of Parse Server 8.
Tasks
Common
- Freeze current LTS branch
release-#.x.xin GitHub repo settings - Publish final releases on
betaandreleasebranches - Ensure all branches
alpha,beta,releaseare on same commit - Add new LTS branch
release-#.x.x - Update Snyk branches to monitor
- Remove monitoring old LTS branch, add new LTS branch
- Updare .releaserc.js for new LTS branch
- 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
- feat: Increase required minimum Node versions to
18.20.4,20.18.0,22.12.0#9521
- 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 versions to
6.0.19,7.0.16,8.0.4#9531
- Remove MongoDB versions from CI in
- Remove support for Postgres / PostGIS versions that have reached their EOL #9532
- Remove Postgres versions from CI in
ci.yml - Remove tests that target only removed Postgres versions
- Remove Postgres versions from CI in
- Remove deprecated Parse Server options
- Update release config LTS branch to new major version (preparatory step for when the new to-be-released major version will become the LTS version on the
release.#.x.xbranch in the future) - Merge latest dependencies
- Parse JS SDK: feat: Upgrade to Parse JS SDK 6.0.0 #9624
- Push adapter: already latest version
- Merge any other breaking changes that have been held-off for a major release
Excluded from this release (with explanation)
- refactor: Upgrade @graphql-yoga/node from 2.6.0 to 3.9.1 #9103 (only close, no merge)
- refactor: Bump graphql-upload from 15.0.2 to 17.0.0 #9342 (unclear when it can be merged)
Notes
- Releases on the LTS branch will fail until the next stable release on the
releasebranch, see here why.
Activity
parse-github-assistant commentedon Oct 23, 2024
Thanks for opening this issue!
[-]Parse Server 8[/-][+]Prepare Parse Server 8 release[/+]mtrezza commentedon Oct 23, 2024
@parse-community/server Please feel free to comment for any other things that should be included in the Parse Server 8 release, specially regarding PRs with breaking changes.
Moumouls commentedon Oct 24, 2024
Not breaking but i'll be happy if we can merge these ones, it's not breaking change but helps developers to achieve advanced uses cases: https://github.com/parse-community/parse-server/pulls/Moumouls
I'll also take a look @mtrezza about differences with my fork, to check if i've some interesting contribution to send to the community repo
I've also a PR idea about avoiding to load some adapters by default if an explicit adapter is provided (for example Postgres is always loaded even if a developer use mongo), it could help to reduce start up time of the server and also reduce integration tests of a developer stack
mtrezza commentedon Oct 24, 2024
Sounds good!
This thread is specifically about Parse Server 8 preparations (what we can realistically achieve and merge until Dec 2024). The focus here is on breaking changes, as these are easier to do with a major server release.
Everything else can be merged at any point in time after Parse Server 8 release. So all other suggestions, are best discussed by opening separate issues.
Regarding Postgres, see #8715.
[-]Prepare Parse Server 8 release[/-][+]Prepare release of Parse Server 8[/+]ngockhanhbl commentedon Dec 30, 2024
I hope this issue will be resolved in the future
#1686
mtrezza commentedon Mar 4, 2025
Closed via #9628