Releases: parse-community/parse-server
Releases · parse-community/parse-server
6.0.0-alpha.26
6.0.0-alpha.26 (2023-01-20)
Bug Fixes
6.0.0-alpha.25
6.0.0-alpha.25 (2023-01-16)
Features
6.0.0-alpha.24
6.0.0-alpha.23
6.0.0-alpha.23 (2023-01-08)
Features
- Access the internal scope of Parse Server using the new
maintenanceKey
; the internal scope contains unofficial and undocumented fields (prefixed with underscore_
) which are used internally by Parse Server; you may want to manipulate these fields for out-of-band changes such as data migration or correction tasks; changes within the internal scope of Parse Server may happen at any time without notice or changelog entry, it is therefore recommended to look at the source code of Parse Server to understand the effects of manipulating internal fields before using the key; it is discouraged to use themaintenanceKey
for routine operations in a production environment; see access scopes (#8212) (f3bcc93)
BREAKING CHANGES
- Fields in the internal scope of Parse Server (prefixed with underscore
_
) are only returned using the newmaintenanceKey
; previously themasterKey
allowed reading of internal fields; see access scopes for a comparison of the keys' access permissions (#8212) (f3bcc93)
6.0.0-alpha.22
6.0.0-alpha.22 (2023-01-08)
Features
BREAKING CHANGES
- The method
ParseServer.verifyServerUrl
now returns a promise instead of a callback. (ffa4974)
6.0.0-alpha.21
6.0.0-alpha.20
6.0.0-alpha.19
6.0.0-alpha.18
6.0.0-alpha.18 (2023-01-05)
Bug Fixes
- The client IP address may be determined incorrectly in some cases; this fixes a security vulnerability in which the Parse Server option
masterKeyIps
may be circumvented, see GHSA-vm5r-c87r-pf6x (#8372) (892040d)
BREAKING CHANGES
- The mechanism to determine the client IP address has been rewritten; to correctly determine the IP address it is now required to set the Parse Server option
trustProxy
accordingly if Parse Server runs behind a proxy server, see the express framework's trust proxy setting (#8372) (892040d)