build: Release #9628
Merged
build: Release #9628
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
…, `22.12.0` (parse-community#9521) BREAKING CHANGE: This releases increases the required minimum Node versions to 18.20.4, 20.18.0, 22.12.0 and removes unofficial support for Node 19.
# [8.0.0-alpha.1](parse-community/parse-server@7.4.0-alpha.7...8.0.0-alpha.1) (2025-01-11) ### Features * Increase required minimum Node versions to `18.20.4`, `20.18.0`, `22.12.0` ([parse-community#9521](parse-community#9521)) ([4e151cd](parse-community@4e151cd)) ### BREAKING CHANGES * This releases increases the required minimum Node versions to 18.20.4, 20.18.0, 22.12.0 and removes unofficial support for Node 19. ([4e151cd](4e151cd))
# [8.0.0-alpha.2](parse-community/parse-server@8.0.0-alpha.1...8.0.0-alpha.2) (2025-01-11) ### Bug Fixes * Push adapter not loading on some versions of Node 22 ([parse-community#9524](parse-community#9524)) ([ff7f671](parse-community@ff7f671))
…`, `8.0.4` (parse-community#9531) BREAKING CHANGE: This releases increases the required minimum MongoDB versions to `6.0.19`, `7.0.16`, `8.0.4` and removes support for MongoDB `4`, `5`.
# [8.0.0-alpha.3](parse-community/parse-server@8.0.0-alpha.2...8.0.0-alpha.3) (2025-01-12) ### Features * Increase required minimum MongoDB versions to `6.0.19`, `7.0.16`, `8.0.4` ([parse-community#9531](parse-community#9531)) ([871e508](parse-community@871e508)) ### BREAKING CHANGES * This releases increases the required minimum MongoDB versions to `6.0.19`, `7.0.16`, `8.0.4` and removes support for MongoDB `4`, `5`. ([871e508](871e508))
# [8.0.0-alpha.4](parse-community/parse-server@8.0.0-alpha.3...8.0.0-alpha.4) (2025-01-12) ### Features * Deprecate `PublicAPIRouter` in favor of `PagesRouter` ([parse-community#9526](parse-community#9526)) ([7f66629](parse-community@7f66629))
…nCloudFunction` to `true` (parse-community#9527) BREAKING CHANGE: The default value of Parse Server option `encodeParseObjectInCloudFunction` changes to `true`; the option has been deprecated and will be removed in a future version.
# [8.0.0-alpha.5](parse-community/parse-server@8.0.0-alpha.4...8.0.0-alpha.5) (2025-01-12) ### Features * Change default value of Parse Server option `encodeParseObjectInCloudFunction` to `true` ([parse-community#9527](parse-community#9527)) ([5c5ad69](parse-community@5c5ad69)) ### BREAKING CHANGES * The default value of Parse Server option `encodeParseObjectInCloudFunction` changes to `true`; the option has been deprecated and will be removed in a future version. ([5c5ad69](5c5ad69))
….3` (parse-community#9538) BREAKING CHANGE: This releases increases the required minimum versions to Postgres `15`, PostGIS `3.3` and removes support for Postgres `13`, `14`, PostGIS `3.1`, `3.2`.
# [8.0.0-alpha.6](parse-community/parse-server@8.0.0-alpha.5...8.0.0-alpha.6) (2025-01-12) ### Features * Increase required minimum versions to Postgres `15`, PostGIS `3.3` ([parse-community#9538](parse-community#9538)) ([89c9b54](parse-community@89c9b54)) ### BREAKING CHANGES * This releases increases the required minimum versions to Postgres `15`, PostGIS `3.3` and removes support for Postgres `13`, `14`, PostGIS `3.1`, `3.2`. ([89c9b54](89c9b54))
…connectTimeoutMS`, `socketTimeoutMS` (parse-community#9522)
# [8.0.0-alpha.10](parse-community/parse-server@8.0.0-alpha.9...8.0.0-alpha.10) (2025-02-01) ### Bug Fixes * Security upgrade node from 20.17.0-alpine3.20 to 20.18.2-alpine3.20 ([parse-community#9583](parse-community#9583)) ([8f85ae2](parse-community@8f85ae2))
# [8.0.0-alpha.11](parse-community/parse-server@8.0.0-alpha.10...8.0.0-alpha.11) (2025-02-12) ### Features * Add dynamic master key by setting Parse Server option `masterKey` to a function ([parse-community#9582](parse-community#9582)) ([6f1d161](parse-community@6f1d161))
# [8.0.0-alpha.12](parse-community/parse-server@8.0.0-alpha.11...8.0.0-alpha.12) (2025-02-24) ### Bug Fixes * LiveQueryServer crashes using cacheAdapter on disconnect from Redis 4 server ([parse-community#9616](parse-community#9616)) ([bbc6bd4](parse-community@bbc6bd4))
…ss (parse-community#8488) BREAKING CHANGE: This removes the username from the email verification and password reset process to prevent storing personally identifiable information (PII) in server and infrastructure logs. Customized HTML pages or emails related to email verification and password reset may need to be adapted accordingly. See the new templates that come bundled with Parse Server and the [migration guide](https://github.com/parse-community/parse-server/blob/alpha/8.0.0.md) for more details.
# [8.0.0-alpha.13](parse-community/parse-server@8.0.0-alpha.12...8.0.0-alpha.13) (2025-03-02) ### Bug Fixes * Remove username from email verification and password reset process ([parse-community#8488](parse-community#8488)) ([d21dd97](parse-community@d21dd97)) ### BREAKING CHANGES * This removes the username from the email verification and password reset process to prevent storing personally identifiable information (PII) in server and infrastructure logs. Customized HTML pages or emails related to email verification and password reset may need to be adapted accordingly. See the new templates that come bundled with Parse Server and the [migration guide](https://github.com/parse-community/parse-server/blob/alpha/8.0.0.md) for more details. ([d21dd97](d21dd97))
BREAKING CHANGE: This upgrades to the Parse JS SDK 6.0.0. See the [change log](https://github.com/parse-community/Parse-SDK-JS/releases/tag/6.0.0) of the Parse JS SDK for breaking changes and more details.
# [8.0.0-alpha.14](parse-community/parse-server@8.0.0-alpha.13...8.0.0-alpha.14) (2025-03-02) ### Features * Upgrade to Parse JS SDK 6.0.0 ([parse-community#9624](parse-community#9624)) ([bf9db75](parse-community@bf9db75)) ### BREAKING CHANGES * This upgrades to the Parse JS SDK 6.0.0. See the [change log](https://github.com/parse-community/Parse-SDK-JS/releases/tag/6.0.0) of the Parse JS SDK for breaking changes and more details. ([bf9db75](bf9db75))
BREAKING CHANGE: This upgrades the internally used Express framework from version 4 to 5, which may be a breaking change. If Parse Server is set up to be mounted on an Express application, we recommend to also use version 5 of the Express framework to avoid any compatibility issues. Note that even if there are no issues after upgrading, future releases of Parse Server may introduce issues if Parse Server internally relies on Express 5-specific features which are unsupported by the Express version on which it is mounted. See the Express [migration guide](https://expressjs.com/en/guide/migrating-5.html) and [release announcement](https://expressjs.com/2024/10/15/v5-release.html#breaking-changes) for more info.
# [8.0.0-alpha.15](parse-community/parse-server@8.0.0-alpha.14...8.0.0-alpha.15) (2025-03-03) ### Features * Upgrade to express 5.0.1 ([parse-community#9530](parse-community#9530)) ([e0480df](parse-community@e0480df)) ### BREAKING CHANGES * This upgrades the internally used Express framework from version 4 to 5, which may be a breaking change. If Parse Server is set up to be mounted on an Express application, we recommend to also use version 5 of the Express framework to avoid any compatibility issues. Note that even if there are no issues after upgrading, future releases of Parse Server may introduce issues if Parse Server internally relies on Express 5-specific features which are unsupported by the Express version on which it is mounted. See the Express [migration guide](https://expressjs.com/en/guide/migrating-5.html) and [release announcement](https://expressjs.com/2024/10/15/v5-release.html#breaking-changes) for more info. ([e0480df](e0480df))
Thanks for opening this pull request! |
23 tasks
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.
Closes: #9366