|
2 | 2 |
|
3 | 3 | Jump directly to a version: |
4 | 4 |
|
5 | | -| 4.x | |
6 | | -|-------------------| |
7 | | -| [**4.5.0 (latest release)**](#450) | |
8 | | -| [4.4.0](#440) | |
9 | | -| [4.3.0](#430) | |
10 | | -| [4.2.0](#420) | |
11 | | -| [4.1.0](#410) | |
12 | | -| [4.0.2](#402) | |
13 | | -| [4.0.1](#401) | |
14 | | -| [4.0.0](#400) | |
| 5 | +| 4.x | |
| 6 | +|--------------------------------------| |
| 7 | +| [**4.10.3 (latest release)**](#4103) | |
| 8 | +| [4.10.2](#4102) | |
| 9 | +| [4.10.1](#4101) | |
| 10 | +| [4.10.0](#4100) | |
| 11 | +| [4.5.2](#452) | |
| 12 | +| [4.5.1](#451) | |
| 13 | +| [4.5.0](#450) | |
| 14 | +| [4.4.0](#440) | |
| 15 | +| [4.3.0](#430) | |
| 16 | +| [4.2.0](#420) | |
| 17 | +| [4.1.0](#410) | |
| 18 | +| [4.0.2](#402) | |
| 19 | +| [4.0.1](#401) | |
| 20 | +| [4.0.0](#400) | |
15 | 21 |
|
16 | 22 | <details> |
17 | 23 | <summary>Previous Versions</summary> |
@@ -88,28 +94,30 @@ Jump directly to a version: |
88 | 94 | ___ |
89 | 95 |
|
90 | 96 | ## Unreleased (Master Branch) |
91 | | -[Full Changelog](https://github.com/parse-community/parse-server/compare/4.5.0...master) |
| 97 | +[Full Changelog](https://github.com/parse-community/parse-server/compare/4.10.3...master) |
| 98 | + |
92 | 99 | ### Breaking Changes |
93 | 100 | - 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) |
94 | 101 | - 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) |
95 | 102 | - Removed [parse-server-simple-mailgun-adapter](https://github.com/parse-community/parse-server-simple-mailgun-adapter) dependency; to continue using the adapter it has to be explicitly installed (Manuel Trezza) [#7321](https://github.com/parse-community/parse-server/pull/7321) |
96 | 103 | - Remove support for MongoDB 3.6 which has reached its End-of-Life date and PostgreSQL 10 (Manuel Trezza) [#7315](https://github.com/parse-community/parse-server/pull/7315) |
97 | 104 | - Remove support for Node 10 which has reached its End-of-Life date (Manuel Trezza) [#7314](https://github.com/parse-community/parse-server/pull/7314) |
98 | 105 | - Remove S3 Files Adapter from Parse Server, instead install separately as `@parse/s3-files-adapter` (Manuel Trezza) [#7324](https://github.com/parse-community/parse-server/pull/7324) |
| 106 | + |
99 | 107 | ### Notable Changes |
100 | 108 | - Added Parse Server Security Check to report weak security settings (Manuel Trezza, dblythy) [#7247](https://github.com/parse-community/parse-server/issues/7247) |
101 | 109 | - EXPERIMENTAL: Added new page router with placeholder rendering and localization of custom and feature pages such as password reset and email verification (Manuel Trezza) [#7128](https://github.com/parse-community/parse-server/pull/7128) |
102 | 110 | - EXPERIMENTAL: Added custom routes to easily customize flows for password reset, email verification or build entirely new flows (Manuel Trezza) [#7231](https://github.com/parse-community/parse-server/pull/7231) |
103 | 111 | - Added Deprecation Policy to govern the introduction of breaking changes in a phased pattern that is more predictable for developers (Manuel Trezza) [#7199](https://github.com/parse-community/parse-server/pull/7199) |
104 | 112 | - Add REST API endpoint `/loginAs` to create session of any user with master key; allows to impersonate another user. (GormanFletcher) [#7406](https://github.com/parse-community/parse-server/pull/7406) |
105 | 113 | - Add official support for MongoDB 5.0 (Manuel Trezza) [#7469](https://github.com/parse-community/parse-server/pull/7469) |
| 114 | +- Add issue bot (Manuel Trezza) [#7523](https://github.com/parse-community/parse-server/pull/7523) |
106 | 115 |
|
107 | 116 | ### Other Changes |
108 | 117 | - Support native mongodb syntax in aggregation pipelines (Raschid JF Rafeally) [#7339](https://github.com/parse-community/parse-server/pull/7339) |
109 | 118 | - Fix error when a not yet inserted job is updated (Antonio Davi Macedo Coelho de Castro) [#7196](https://github.com/parse-community/parse-server/pull/7196) |
110 | 119 | - request.context for afterFind triggers (dblythy) [#7078](https://github.com/parse-community/parse-server/pull/7078) |
111 | 120 | - Winston Logger interpolating stdout to console (dplewis) [#7114](https://github.com/parse-community/parse-server/pull/7114) |
112 | | -- Move graphql-tag from devDependencies to dependencies (Antonio Davi Macedo Coelho de Castro) [#7183](https://github.com/parse-community/parse-server/pull/7183) |
113 | 121 | - Added convenience method `Parse.Cloud.sendEmail(...)` to send email via email adapter in Cloud Code (dblythy) [#7089](https://github.com/parse-community/parse-server/pull/7089) |
114 | 122 | - LiveQuery support for $and, $nor, $containedBy, $geoWithin, $geoIntersects queries (dplewis) [#7113](https://github.com/parse-community/parse-server/pull/7113) |
115 | 123 | - Supporting patterns in LiveQuery server's config parameter `classNames` (Nes-si) [#7131](https://github.com/parse-community/parse-server/pull/7131) |
|
139 | 147 | - Fix LiveQuery server crash when using $all query operator on a missing object key (Jason Posthuma) [#7421](https://github.com/parse-community/parse-server/pull/7421) |
140 | 148 | - Added runtime deprecation warnings (Manuel Trezza) [#7451](https://github.com/parse-community/parse-server/pull/7451) |
141 | 149 | - 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) |
| 150 | +- Add CI check to add changelog entry (Manuel Trezza) [#7512](https://github.com/parse-community/parse-server/pull/7512) |
| 151 | +- Refactor: uniform issue templates across repos (Manuel Trezza) [#7528](https://github.com/parse-community/parse-server/pull/7528) |
| 152 | +- ci: bump ci environment (Manuel Trezza) [#7539](https://github.com/parse-community/parse-server/pull/7539) |
| 153 | + |
| 154 | +## 4.10.3 |
| 155 | +[Full Changelog](https://github.com/parse-community/parse-server/compare/4.10.2...4.10.3) |
| 156 | + |
| 157 | +### Security Fixes |
| 158 | +- Validate `explain` query parameter to avoid a server crash due to MongoDB bug [NODE-3463](https://jira.mongodb.org/browse/NODE-3463) (Kartal Kaan Bozdogan) [GHSA-xqp8-w826-hh6x](https://github.com/parse-community/parse-server/security/advisories/GHSA-xqp8-w826-hh6x) |
| 159 | + |
| 160 | +## 4.10.2 |
| 161 | +[Full Changelog](https://github.com/parse-community/parse-server/compare/4.10.1...4.10.2) |
| 162 | + |
| 163 | +### Other Changes |
| 164 | +- Move graphql-tag from devDependencies to dependencies (Antonio Davi Macedo Coelho de Castro) [#7183](https://github.com/parse-community/parse-server/pull/7183) |
| 165 | + |
| 166 | +## 4.10.1 |
| 167 | +[Full Changelog](https://github.com/parse-community/parse-server/compare/4.10.0...4.10.1) |
| 168 | + |
| 169 | +### Security Fixes |
| 170 | +- Updated to Parse JS SDK 3.3.0 and other security fixes (Manuel Trezza) [#7508](https://github.com/parse-community/parse-server/pull/7508) |
| 171 | + |
| 172 | +> ⚠️ 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). |
| 173 | +
|
| 174 | +## 4.10.0 |
| 175 | +[Full Changelog](https://github.com/parse-community/parse-server/compare/4.5.2...4.10.0) |
| 176 | + |
| 177 | +*Versions >4.5.2 and <4.10.0 are skipped.* |
| 178 | + |
| 179 | +> ⚠️ A security incident caused a number of incorrect version tags to be pushed to the Parse Server repository. These version tags linked to a personal fork of a contributor who had write access to the repository. The code to which these tags linked has not been reviewed or approved by Parse Platform. Even though no releases were published with these incorrect versions, it was possible to define a Parse Server dependency that pointed to these version tags, for example if you defined this dependency: |
| 180 | +> ```js |
| 181 | +> "parse-server": "[email protected]:parse-community/parse-server.git#4.9.3" |
| 182 | +> ``` |
| 183 | +> |
| 184 | +> We have since deleted the incorrect version tags, but they may still show up if your personal fork on GitHub or locally. We do not know when these tags have been pushed to the Parse Server repository, but we first became aware of this issue on July 21, 2021. We are not aware of any malicious code or concerns related to privacy, security or legality (e.g. proprietary code). However, it has been reported that some functionality does not work as expected and the introduction of security vulnerabilities cannot be ruled out. |
| 185 | +> |
| 186 | +> You may be also affected if you used the Bitnami image for Parse Server. Bitnami picked up the incorrect version tag `4.9.3` and published a new Bitnami image for Parse Server. |
| 187 | +> |
| 188 | +>**If you are using any of the affected versions, we urgently recommend to upgrade to version `4.10.0`.** |
| 189 | +
|
| 190 | +## 4.5.2 |
| 191 | +[Full Changelog](https://github.com/parse-community/parse-server/compare/4.5.0...4.5.2) |
| 192 | +
|
| 193 | +### Security Fixes |
| 194 | +- SECURITY FIX: Fixes incorrect session property `authProvider: password` of anonymous users. When signing up an anonymous user, the session field `createdWith` indicates incorrectly that the session has been created using username and password with `authProvider: password`, instead of an anonymous sign-up with `authProvider: anonymous`. This fixes the issue by setting the correct `authProvider: anonymous` for future sign-ups of anonymous users. This fix does not fix incorrect `authProvider: password` for existing sessions of anonymous users. Consider this if your app logic depends on the `authProvider` field. (Corey Baker) [GHSA-23r4-5mxp-c7g5](https://github.com/parse-community/parse-server/security/advisories/GHSA-23r4-5mxp-c7g5) |
| 195 | +
|
| 196 | +## 4.5.1 |
| 197 | +*This version was published by mistake and was deprecated.* |
142 | 198 |
|
143 | | -___ |
144 | 199 | ## 4.5.0 |
145 | 200 | [Full Changelog](https://github.com/parse-community/parse-server/compare/4.4.0...4.5.0) |
146 | 201 | ### Breaking Changes |
|
0 commit comments