Skip to content

Releases: parse-community/parse-server

4.3.0

19 Jul 17:41
6f060e0
Compare
Choose a tag to compare

Full Changelog

  • PERFORMANCE: Optimizing pointer CLP query decoration done by DatabaseController#addPointerPermissions #6747. Thanks to mess-lelouch.
  • SECURITY: Fix security breach on GraphQL viewer 78239ac, secuity advisory. Thanks to Antoine Cormouls.
  • FIX: Save context not present if direct access enabled #6764. Thanks to Omair Vaiyani.
  • NEW: Before Connect + Before Subscribe #6793. Thanks to dblythy.
  • FIX: Add version to playground to fix CDN #6804. Thanks to Antoine Cormouls.
  • NEW (EXPERIMENTAL): Idempotency enforcement for client requests. This deduplicates requests where the client intends to send one request to Parse Server but due to network issues the server receives the request multiple times. Caution, this is an experimental feature that may not be appropriate for production. #6748. Thanks to Manuel Trezza.
  • FIX: Add production Google Auth Adapter instead of using the development url #6734. Thanks to SebC..
  • IMPROVE: Run Prettier JS Again Without requiring () on arrow functions #6796. Thanks to Diamond Lewis.
  • IMPROVE: Run Prettier JS #6795. Thanks to Diamond Lewis.
  • IMPROVE: Replace bcrypt with @node-rs/bcrypt #6794. Thanks to LongYinan.
  • IMPROVE: Make clear description of anonymous user #6655. Thanks to Jerome De Leon.
  • IMPROVE: Simplify GraphQL merge system to avoid js ref bugs #6791. Thanks to Antoine Cormouls.
  • NEW: Pass context in beforeDelete, afterDelete, beforeFind and Parse.Cloud.run #6666. Thanks to yog27ray.
  • NEW: Allow passing custom gql schema function to ParseServer#start options #6762. Thanks to Luca.
  • NEW: Allow custom cors origin header #6772. Thanks to Kevin Yao.
  • FIX: Fix context for cascade-saving and saving existing object #6735. Thanks to Manuel.
  • NEW: Add file bucket encryption using fileKey #6765. Thanks to Corey Baker.
  • FIX: Removed gaze from dev dependencies and removed not working dev script #6745. Thanks to Vincent Semrau.
  • IMPROVE: Upgrade graphql-tools to v6 #6701. Thanks to Yaacov Rydzinski.
  • NEW: Support Metadata in GridFSAdapter #6660. Thanks to Diamond Lewis.
  • NEW: Allow to unset file from graphql #6651. Thanks to Antoine Cormouls.
  • NEW: Handle shutdown for RedisCacheAdapter #6658. Thanks to promisenxu.
  • FIX: Fix explain on user class #6650. Thanks to Manuel.
  • FIX: Fix read preference for aggregate #6585. Thanks to Manuel.
  • NEW: Add context to Parse.Object.save #6626. Thanks to Manuel.
  • NEW: Adding ssl config params to Postgres URI #6580. Thanks to Corey Baker.
  • FIX: Travis postgres update: removing unnecessary start of mongo-runner #6594. Thanks to Corey Baker.
  • FIX: ObjectId size for Pointer in Postgres #6619. Thanks to Corey Baker.
  • IMPROVE: Improve a test case #6629. Thanks to Gordon Sun.
  • NEW: Allow to resolve automatically Parse Type fields from Custom Schema #6562. Thanks to Antoine Cormouls.
  • FIX: Remove wrong console log in test #6627. Thanks to Gordon Sun.
  • IMPROVE: Graphql tools v5 #6611. Thanks to Yaacov Rydzinski.
  • FIX: Catch JSON.parse and return 403 properly #6589. Thanks to Gordon Sun.
  • PERFORMANCE: Allow covering relation queries with minimal index #6581. Thanks to Noah Silas.
  • FIX: Fix Postgres group aggregation #6522. Thanks to Siddharth Ramesh.
  • NEW: Allow set user mapped from JWT directly on request #6411. Thanks to Gordon Sun.

4.2.0

03 Apr 16:54
1045eeb
Compare
Choose a tag to compare

Full Changelog

4.1.0

03 Mar 19:42
b9742b6
Compare
Choose a tag to compare

Full Changelog

SECURITY RELEASE: see advisory for details

4.0.2

02 Mar 18:47
bde8ab6
Compare
Choose a tag to compare

Full Changelog

BREAKING CHANGES:

  1. Remove Support for Mongo 3.2 & 3.4. The new minimum supported version is Mongo 3.6.
  2. Change username and email validation to be case insensitive. This change should be transparent in most use cases. The validation behavior should now behave 'as expected'. See #5634 for details.

Special Note on Upgrading to Parse Server 4.0.0 and above

In addition to the breaking changes noted above, #5634 introduces a two new case insensitive indexes on the User collection. Special care should be taken when upgrading to this version to ensure that:

  1. The new indexes can be successfully created (see issue #6465 for details on a potential issue for your installation).

  2. Care is taken ensure that there is adequate compute capacity to create the index in the background while still servicing requests.

4.0.1

29 Feb 01:36
cd06a02
Compare
Choose a tag to compare

BREAKING CHANGES:

  1. Remove Support for Mongo 3.2 & 3.4. The new minimum supported version is Mongo 3.6.
  2. Change username and email validation to be case insensitive. This change should be transparent in most use cases. The validation behavior should now behave 'as expected'. See #5634 for details.

Special Note on Upgrading to Parse Server 4.0.0 and above

In addition to the breaking changes noted above, #5634 introduces a two new case insensitive indexes on the User collection. Special care should be taken when upgrading to this version to ensure that:

  1. The new indexes can be successfully created (see issue #6465 for details on a potential issue for your installation).

  2. Care is taken ensure that there is adequate compute capacity to create the index in the background while still servicing requests.

  • FIX: correct 'new' travis config to properly deploy. See #6452. Thanks to Arthur Cinader.
  • FIX: Better message on not allowed to protect default fields. See #6439.Thanks to Old Grandpa

4.0.0

28 Feb 23:26
4291f2b
Compare
Choose a tag to compare

BREAKING CHANGES:

  1. Remove Support for Mongo 3.2 & 3.4. The new minimum supported version is Mongo 3.6.
  2. Change username and email validation to be case insensitive. This change should be transparent in most use cases. The validation behavior should now behave 'as expected'. See #5634 for details.

Special Note on Upgrading to Parse Server 4.0.0 and above

In addition to the breaking changes noted above, #5634 introduces a two new case insensitive indexes on the User collection. Special care should be taken when upgrading to this version to ensure that:

  1. The new indexes can be successfully created (see issue #6465 for details on a potential issue for your installation).

  2. Care is taken ensure that there is adequate compute capacity to create the index in the background while still servicing requests.

Full Changelog

3.10.0

08 Jan 17:19
0fc811a
Compare
Choose a tag to compare

Full Changelog

3.9.0

12 Sep 22:31
6edaa2e
Compare
Choose a tag to compare

3.8.0

27 Aug 02:44
ce2405a
Compare
Choose a tag to compare

See the change log for details.

3.7.2

31 Jul 09:19
fe18fe0
Compare
Choose a tag to compare
  • FIX: Live Query was failing on release 3.7.1