Bump parse from 2.17.0 to 3.3.0

[dependabot-preview]

Bumps parse from 2.17.0 to 3.3.0.

Release notes

Sourced from parse's releases.

3.3.0

Improvements

• Improve support for nested keys (#1364)
• Doc improvement (#1349)
• Add npm version ci check (#1345)
• Added an error code for geospatial index failures (#1342)
• Added date support to OfflineQuery class (#1344)

Fixes

• Fix react native build (#1381)
• Fix weapp uuid error (#1356)
• Fix EventEmitter undefined on React Native 0.64 (#1351)

3.2.0

Breaking Changes

• Remove deletion of Anonymous User on logout (#1324) See https://community.parseplatform.org/t/anonymous-user-destroyed-on-logout/1425

Improvements

• Allow multiple classNames for Parse.Object.registerSubclass (#1315)

const classNames = ['ClassOne', 'ClassTwo', 'ClassThree'];
for (const className of classNames) {
  Parse.Object.registerSubclass(className, CustomClass);
}

Fixes

• Fixes build for WeChat WeApp, to reduce package size, see [issue/#1331](parse-community/Parse-SDK-JS#1331)

3.1.0

Breaking Changes Parse.Push.send will now return the pushStatusId instead of { result: true }

Features

• Add Server Health Check Parse.getServerHealth() (#1307)
• Allow saving with custom objectId Parse.allowCustomObjectId = true (#1309)
• Parse.Push.send now returns pushStatusId (#1302)
• Add Parse.Push.getPushStatus (#1302)

Improvements

• Add modifiers to query.startsWith (#1306)
• Add modifiers to query.endsWith (#1306)

Fixes

• EventuallyQueue now polls against /health endpoint, caused 403 forbidden side effect (#1305)
• Allow nested increment on undefined fields (#1303)
• Handle increment on nested fields any level deep (#1301)

3.0.0

... (truncated)

Changelog

Sourced from parse's changelog.

3.3.0

Full Changelog

Improvements

• Improve support for nested keys (#1364)
• Doc improvement (#1349)
• Add npm version ci check (#1345)
• Added an error code for geospatial index failures (#1342)
• Added date support to OfflineQuery class (#1344)

Fixes

• Fix react native build (#1381)
• Fix weapp uuid error (#1356)
• Fix EventEmitter undefined on React Native 0.64 (#1351)

3.2.0

Full Changelog

Breaking Changes

• Remove deletion of Anonymous User on logout (#1324) See https://community.parseplatform.org/t/anonymous-user-destroyed-on-logout/1425

Improvements

• Allow multiple classNames for Parse.Object.registerSubclass (#1315)

const classNames = ['ClassOne', 'ClassTwo', 'ClassThree'];
for (const className of classNames) {
  Parse.Object.registerSubclass(className, CustomClass);
}

Fixes

• Fixes build for WeChat WeApp, to reduce package size, see [issue/#1331](parse-community/Parse-SDK-JS#1331)

3.1.0

Full Changelog

Breaking Changes Parse.Push.send will now return the pushStatusId instead of { result: true }

Features

• Add Server Health Check Parse.getServerHealth() (#1307)
• Allow saving with custom objectId Parse.allowCustomObjectId = true (#1309)
• Parse.Push.send now returns pushStatusId (#1302)
• Add Parse.Push.getPushStatus (#1302)

Improvements

• Add modifiers to query.startsWith (#1306)
• Add modifiers to query.endsWith (#1306)

... (truncated)

Commits

• 2e7a406 Release v3.3.0 (#1383)
• 720b954 fix: upgrade ws from 7.4.6 to 7.5.0 (#1382)
• 886f17d Fix react native build (#1381)
• 53768db fix: upgrade @​babel/runtime-corejs3 from 7.14.5 to 7.14.6 (#1379)
• ea9179f fix: upgrade @​babel/runtime from 7.14.5 to 7.14.6 (#1380)
• 0bd120e fix: upgrade @​babel/runtime from 7.14.0 to 7.14.5 (#1376)
• af8b9c3 fix: upgrade @​babel/runtime-corejs3 from 7.14.0 to 7.14.5 (#1377)
• e4e2425 fix: upgrade idb-keyval from 5.0.5 to 5.0.6 (#1374)
• 005321f fix: package.json & package-lock.json to reduce vulnerabilities (#1370)
• 0985f59 build(deps): bump browserslist from 4.16.4 to 4.16.6 (#1369)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by parseadmin, a new releaser for parse since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)