7.3.0-alpha.3

7.3.0-alpha.3 (2024-07-17)

Bug Fixes

• Parse Server installation fails due to post install script incorrectly parsing required min. Node version (#9216) (0fa82a5)

7.3.0-alpha.2

7.3.0-alpha.2 (2024-07-17)

Bug Fixes

• Parse Server databaseOptions nested keys incorrectly identified as invalid (#9213) (77206d8)

7.3.0-alpha.1

7.3.0-alpha.1 (2024-07-09)

Features

• Add Node 22 support (#9187) (7778471)

7.2.0

7.2.0 (2024-07-09)

Bug Fixes

• Invalid push notification tokens are not cleaned up from database for FCM API v2 (#9173) (284da09)

Features

• Add support for dot notation on array fields of Parse Object (#9115) (cf4c880)
• Upgrade to @parse/push-adapter 6.4.0 (#9182) (ef1634b)
• Upgrade to Parse JS SDK 5.3.0 (#9180) (dca187f)

7.2.0-beta.1

7.2.0-beta.1 (2024-07-09)

Bug Fixes

• Invalid push notification tokens are not cleaned up from database for FCM API v2 (#9173) (284da09)

Features

• Add support for dot notation on array fields of Parse Object (#9115) (cf4c880)
• Upgrade to @parse/push-adapter 6.4.0 (#9182) (ef1634b)
• Upgrade to Parse JS SDK 5.3.0 (#9180) (dca187f)

7.1.0-alpha.16

7.1.0-alpha.16 (2024-07-08)

Features

• Add support for dot notation on array fields of Parse Object (#9115) (cf4c880)

7.1.0-alpha.15

7.1.0-alpha.15 (2024-07-08)

Features

• Upgrade to @parse/push-adapter 6.4.0 (#9182) (ef1634b)

7.1.0-alpha.14

7.1.0-alpha.14 (2024-07-07)

Features

• Upgrade to Parse JS SDK 5.3.0 (#9180) (dca187f)

7.1.0-alpha.13

7.1.0-alpha.13 (2024-07-01)

Bug Fixes

• Invalid push notification tokens are not cleaned up from database for FCM API v2 (#9173) (284da09)

7.1.0

7.1.0 (2024-06-30)

Warning

We recommend to skip this release. This release contains a bug in which a Parse Object property that is an object is converted to an array if the object's nested key name is number-like. For example, a Parse Object property that is stored in the database as object { 0: 'a' } is returned as array ['a']. The bug has been introduced via the Parse JS SDK 5.2.0 which is used in Parse Server Cloud Code. Other Parse client SDKs and the Parse Server REST API are unaffected. For more information see the release notes of Parse JS SDK 5.3.0 in which the bug has been fixed.

Bug Fixes

• Parse.Cloud.startJob and Parse.Push.send not returning status ID when setting Parse Server option directAccess: true (#8766) (5b0efb2)
• Required option not handled correctly for special fields (File, GeoPoint, Polygon) on GraphQL API mutations (#8915) (907ad42)
• Facebook Limited Login not working due to incorrect domain in JWT validation (#9122) (9d0bd2b)
• Live query throws error when constraint notEqualTo is set to null (#8835) (11d3e48)
• Parse Server option extendSessionOnUse not working for session lengths < 24 hours (#9113) (0a054e6)
• Rate limiting can fail when using Parse Server option rateLimit.redisUrl with clusters (#8632) (c277739)
• SQL injection when using Parse Server with PostgreSQL; fixes security vulnerability GHSA-c2hr-cqg6-8j6r (#9167) (2edf1e4)

Features

• Add silent log level for Cloud Code (#8803) (5f81efb)
• Add server security check status security.enableCheck to Features Router (#8679) (b07ec15)
• Prevent Parse Server start in case of unknown option in server configuration (#8987) (8758e6a)
• Upgrade to @parse/push-adapter 6.0.0 (#9066) (18bdbf8)
• Upgrade to @parse/push-adapter 6.2.0 (#9127) (ca20496)
• Upgrade to Parse JS SDK 5.2.0 (#9128) (665b8d5)