Parse Server for Node.js / Express
APACHE-2.0 License
Bot releases are visible (Hide)
Published by parseplatformorg over 2 years ago
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 support is required. (Diamond Lewis, SebC) #7214
400
and Parse Error 105
(INVALID_KEY_NAME
). By default these keywords are: {_bsontype: "Code"}
, constructor
, __proto__
. If you are using any of these keywords in your request data, you can override the default keywords by setting the new Parse Server option requestKeywordDenylist
to []
and specify your own keywords as needed. (GHSA-p6h4-93qp-jhcm) (#7843) (971adb5)fileUpload
parameter in the Parse Server Options (dblythy, Manuel Trezza) #7071
@parse/s3-files-adapter
(Manuel Trezza) #7324
restricted
; the field was a code artifact from a feature that never existed in Open Source Parse Server; if you have been using this field for custom purposes, consider that for new Parse Server installations the field does not exist anymore in the schema, and for existing installations the field default value false
will not be set anymore when creating a new session (Manuel Trezza) #7543
null
. Previously, setting a field value to null
would save a null value in the database, which was not according to the GraphQL specs. To delete a file field use file: null
, the previous way of using file: { file: null }
has become obsolete. (626fad2)/loginAs
to create session of any user with master key; allows to impersonate another user. (GormanFletcher) #7406
enforcePrivateUsers
, which will remove public access by default on new Parse.Users (dblythy) #7319
and
query with relational query condition returns incorrect results (#7593) (174886e)Parse.Cloud.sendEmail(...)
to send email via email adapter in Cloud Code (dblythy) #7089
classNames
(Nes-si) #7131
requireAnyUserRoles
and requireAllUserRoles
for Parse Cloud validator (dblythy) #7097
accountLockout.unlockOnPasswordReset
to automatically unlock account on password reset (Manuel Trezza) #7146
options
to be async (dblythy) #7155
Parse.Cloud.httpRequest
; it is recommended to use a HTTP library instead. (Daniel Blyth) #7595
Published by parseplatformorg over 2 years ago
Published by parseplatformorg over 2 years ago
Published by parseplatformorg over 2 years ago
Published by parseplatformorg over 2 years ago
Published by parseplatformorg over 2 years ago
Published by parseplatformorg over 2 years ago
security vulnerability that allows remote code execution (GHSA-p6h4-93qp-jhcm) (#7841) (886bfd7)
Note that as part of the fix a new security feature scans for sensitive keywords in request data to prevent JavaScript prototype pollution. If such a keyword is found, the request is rejected with HTTP response code 400
and Parse Error 105
(INVALID_KEY_NAME
). By default these keywords are: {_bsontype: "Code"}
, constructor
, __proto__
. If you are using any of these keywords in your request data, you can override the default keywords by setting the new Parse Server option requestKeywordDenylist
to []
and specify your own keywords as needed.
Published by parseplatformorg over 2 years ago
Published by parseplatformorg over 2 years ago
Published by parseplatformorg over 2 years ago
Published by parseplatformorg over 2 years ago
Published by parseplatformorg over 2 years ago
Published by parseplatformorg over 2 years ago
Published by parseplatformorg over 2 years ago
Published by parseplatformorg over 2 years ago
Published by parseplatformorg over 2 years ago
Published by parseplatformorg almost 3 years ago
Published by parseplatformorg almost 3 years ago