Conversation
ghost
added
the
ghost
approved these changes
Oct 15, 2019
ghost
merged commit
beiguancyc
pushed a commit
to beiguancyc/parse-dashboard
that referenced
this pull request
Oct 18, 2019
* parse: (36 commits) prepare for 2.0.4 (parse-community#1347) Only do a complex query for createdAt instead of -createdAt (parse-community#1334) Update parse to the latest version 🚀 (parse-community#1345) Update webpack to the latest version 🚀 (parse-community#1344) Update core-js to the latest version 🚀 (parse-community#1343) Update core-js to the latest version 🚀 (parse-community#1342) Update core-js to the latest version 🚀 (parse-community#1341) Update eslint-plugin-jest to the latest version 🚀 (parse-community#1340) Update eslint-plugin-jest to the latest version 🚀 (parse-community#1339) Update webpack to the latest version 🚀 (parse-community#1338) Update babel7 to the latest version 🚀 (parse-community#1337) Fixed incorrect links to PR details (parse-community#1329) Update babel7 to the latest version 🚀 (parse-community#1335) Update eslint-plugin-react to the latest version 🚀 (parse-community#1327) Update react to the latest version 🚀 (parse-community#1326) Update cross-env to the latest version 🚀 (parse-community#1324) This should resolve parse-community#1297. The objectId was missing from the filter list. (parse-community#1315) Update eslint-plugin-react to the latest version 🚀 (parse-community#1322) Update cross-env to the latest version 🚀 (parse-community#1321) Update eslint-plugin-react to the latest version 🚀 (parse-community#1319) ... # Conflicts: # package-lock.json
This pull request was closed.
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
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.
The dependency parse was updated from
2.7.1to2.8.0.This version is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
Publisher: acinader
License: BSD-3-Clause
Release Notes for 2.8.0
New Features
Fixes
Improvements
Commits
The new version differs by 29 commits ahead by 29, behind by 1.
1e7e628Merge branch 'master' into 2.8.0892636cSupport Parse.File getData cancel (#951)dc26b15Generate _localId as UUID (#956)0e30355⚡️ Release v2.8.08ee9c14Update core-js to the latest version 🚀 (#954)3a255bfUpdate core-js to the latest version 🚀 (#953)23be6cdUpdate core-js to the latest version 🚀 (#952)6f8327cSupport ParseFile upload cancel (#948)cd76082Update babel7 to the latest version 🚀 (#950)1e3bb91Fix deleteIndex and deleteField in ParseSchema (#949)55e5bd2Support compiling on Windows (#947)18fd502Fix require EventEmitter (#946)d0dbdffUpdate babel7 to the latest version 🚀 (#945)5ee76a9Update @babel/runtime-corejs3 to the latest version 🚀 (#944)fee4976Update cross-env to the latest version 🚀 (#940)There are 29 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴