Update parse to version 1.9.0 🚀 #2233
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@greenkeeperio-bot updated the pull request. |
rsouzas
pushed a commit
to back4app/parse-server
that referenced
this pull request
Mar 15, 2017
* chore(package): update parse to version 1.9.0 https://greenkeeper.io/ * Removes Hooks client API as provided by node SDK
rsouzas
pushed a commit
to back4app/parse-server
that referenced
this pull request
Mar 16, 2017
* chore(package): update parse to version 1.9.0 https://greenkeeper.io/ * Removes Hooks client API as provided by node SDK
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
parse just published its new version 1.9.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of parse.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 15 commits .
96eca67Prepare 1.9.0f5f2d3ePrepare 1.9.0-rc141a709dMerge pull request #294 from benjaminmcdonald/patch-1aabbfcdMerge pull request #243 from flovilmart/nodeHooksAPI040e32fUpdate ParseFile.js1d380aaFix error message on Promise reject after resolvece73a6eUpdate ParseFile.js3fad3aeUpdate ParseFile.js117c091Merge pull request #289 from flovilmart/handle-server-set-delete-opd3ef256small nitb07fb7dAdds ability to interpolate delete operationsef2b483Cleaning up ParseLiveQuery, adding some test coverage8a3d011Merge pull request #285 from adamserafini/fix-docs09df0d6Update documentation for Each queries.31c5f1fAdds Hooks API on parse/nodeSee the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade