Skip to content

Commit

Permalink
Updates for 2.0.8
Browse files Browse the repository at this point in the history
  • Loading branch information
gfosco committed Feb 11, 2016
1 parent 6db40f0 commit ea30a98
Show file tree
Hide file tree
Showing 3 changed files with 18 additions and 2 deletions.
15 changes: 15 additions & 0 deletions CHANGELOG.md
@@ -0,0 +1,15 @@
## Parse Server Changelog

### 2.0.8 (2/11/2016)

Add: support for Android and iOS push notifications
Eperimental: Cloud Code validation hooks (can mark as non-experimental after we have docs)
Experimental: support for schemas API (GET and POST only)
Experimental: support for Parse Config (GET and POST only)
Fix: Querying objects with equality constraint on array column
Fix: User logout will remove session token
Fix: Various files related bugs
Fix: Force minimum node version 4.3 due to security issues in earlier version
Performance Improvement: Improved caching


3 changes: 2 additions & 1 deletion README.md
Expand Up @@ -25,6 +25,7 @@ We also have an [example project](https://github.com/ParsePlatform/parse-server-
* fileKey - For migrated apps, this is necessary to provide access to files already hosted on Parse.
* facebookAppIds - An array of valid Facebook application IDs.
* serverURL - URL which will be used by Cloud Code functions to make requests against.
* push - Configuration options for APNS and GCM push. See the [wiki entry](https://github.com/ParsePlatform/parse-server/wiki/Push).

#### Client key options:

Expand Down Expand Up @@ -122,6 +123,7 @@ Now you can just run `$ parse-server` from your command line.
* Pointers
* Users, including Facebook login and anonymous users
* Files
* Push Notifications - See the [wiki entry](https://github.com/ParsePlatform/parse-server/wiki/Push).
* Installations
* Sessions
* Geopoints
Expand All @@ -133,5 +135,4 @@ You can also set up an app on Parse, providing the connection string for your mo

### Not supported

* Push - We did not rebuild a new push delivery system for parse-server, but we are open to working on one together with the community.
* `Parse.User.current()` or `Parse.Cloud.useMasterKey()` in cloud code. Instead of `Parse.User.current()` use `request.user` and instead of `Parse.Cloud.useMasterKey()` pass `useMasterKey: true` to each query. To make queries and writes as a specific user within Cloud Code, you need the user's session token, which is available in `request.user.getSessionToken()`.
2 changes: 1 addition & 1 deletion package.json
@@ -1,6 +1,6 @@
{
"name": "parse-server",
"version": "2.0.7",
"version": "2.0.8",
"description": "An express module providing a Parse-compatible API server",
"main": "lib/index.js",
"repository": {
Expand Down

0 comments on commit ea30a98

Please sign in to comment.