Merge release 4.10.1 (#7511)
* Update CHANGELOG.md * bump version * bumped mongodb@3.6.11
This commit is contained in:
12
CHANGELOG.md
12
CHANGELOG.md
@@ -4,7 +4,8 @@ Jump directly to a version:
|
||||
|
||||
| 4.x |
|
||||
|--------------------------------------|
|
||||
| [**4.10.0 (latest release)**](#4100) |
|
||||
| [**4.10.1 (latest release)**](#4101) |
|
||||
| [4.10.0](#4100) |
|
||||
| [4.5.2](#452) |
|
||||
| [4.5.1](#451) |
|
||||
| [4.5.0](#450) |
|
||||
@@ -91,7 +92,7 @@ Jump directly to a version:
|
||||
___
|
||||
|
||||
## Unreleased (Master Branch)
|
||||
[Full Changelog](https://github.com/parse-community/parse-server/compare/4.10.0...master)
|
||||
[Full Changelog](https://github.com/parse-community/parse-server/compare/4.10.1...master)
|
||||
### Breaking Changes
|
||||
- Improved schema caching through database real-time hooks. Reduces DB queries, decreases Parse Query execution time and fixes a potential schema memory leak. If multiple Parse Server instances connect to the same DB (for example behind a load balancer), set the [Parse Server Option](https://parseplatform.org/parse-server/api/master/ParseServerOptions.html) `databaseOptions.enableSchemaHooks: true` to enable this feature and keep the schema in sync across all instances. Failing to do so will cause a schema change to not propagate to other instances and re-syncing will only happen when these instances restart. The options `enableSingleSchemaCache` and `schemaCacheTTL` have been removed. To use this feature with MongoDB, a replica set cluster with [change stream](https://docs.mongodb.com/manual/changeStreams/#availability) support is required. (Diamond Lewis, SebC) [#7214](https://github.com/parse-community/parse-server/issues/7214)
|
||||
- Added file upload restriction. File upload is now only allowed for authenticated users by default for improved security. To allow file upload also for Anonymous Users or Public, set the `fileUpload` parameter in the [Parse Server Options](https://parseplatform.org/parse-server/api/master/ParseServerOptions.html) (dblythy, Manuel Trezza) [#7071](https://github.com/parse-community/parse-server/pull/7071)
|
||||
@@ -144,6 +145,13 @@ ___
|
||||
- Add ability to pass context of an object via a header, X-Parse-Cloud-Context, for Cloud Code triggers. The header addition allows client SDK's to add context without injecting _context in the body of JSON objects (Corey Baker) [#7437](https://github.com/parse-community/parse-server/pull/7437)
|
||||
- Add CI check to add changelog entry (Manuel Trezza) [#7512](https://github.com/parse-community/parse-server/pull/7512)
|
||||
|
||||
### 4.10.1
|
||||
[Full Changelog](https://github.com/parse-community/parse-server/compare/4.10.0...4.10.1)
|
||||
|
||||
- Updated to Parse JS SDK 3.3.0 and other security fixes (Manuel Trezza) [#7508](https://github.com/parse-community/parse-server/pull/7508)
|
||||
|
||||
> ⚠️ This includes a security fix of the Parse JS SDK where `logIn` will default to `POST` instead of `GET` method. This may require changes in your deployment before you upgrade to this release, see the Parse JS SDK 3.0.0 [release notes](https://github.com/parse-community/Parse-SDK-JS/releases/tag/3.0.0).
|
||||
|
||||
## 4.10.0
|
||||
[Full Changelog](https://github.com/parse-community/parse-server/compare/4.5.2...4.10.0)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user