Bump parse-server from 3.6.0 to 4.1.0

[dependabot[bot]]

Bumps parse-server from 3.6.0 to 4.1.0.

Release notes

Sourced from parse-server's releases.

4.1.0

Full Changelog

SECURITY RELEASE: see advisory for details

• SECURITY FIX: Patch Regex vulnerabilities. See 3a3a5ee. Special thanks to W0lfw00d for identifying and responsibly reporting the vulnerability. Thanks to Antonio Davi Macedo Coelho de Castro for the speedy fix.

4.0.2

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.

• FIX: attempt to get travis to deploy to npmjs again. See #6475. Thanks to Arthur Cinader.

4.0.1

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

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).

Changelog

Sourced from parse-server's changelog.

4.1.0

Full Changelog

SECURITY RELEASE: see advisory for details

• SECURITY FIX: Patch Regex vulnerabilities. See 3a3a5ee. Special thanks to W0lfw00d for identifying and responsibly reporting the vulnerability. Thanks to Antonio Davi Macedo Coelho de Castro for the speedy fix.

4.0.2

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.

• FIX: attempt to get travis to deploy to npmjs again. See #6475. Thanks to Arthur Cinader.

4.0.1

Full Changelog

• 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

Full Changelog

Special Note on Upgrading to Parse Server 4.0.0 and above

In addition to the breaking changes noted below, #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.

• NEW: add hint option to Parse.Query #6322. Thanks to Steve Stencil
• FIX: CLP objectId size validation fix #6332. Thanks to Old Grandpa
• FIX: Add volumes to Docker command #6356. Thanks to Kasra Bigdeli
• NEW: GraphQL 3rd Party LoginWith Support #6371. Thanks to Antoine Cormouls
• FIX: GraphQL Geo Queries #6363. Thanks to Antoine Cormouls
• NEW: GraphQL Nested File Upload #6372. Thanks to Antoine Cormouls
• NEW: Granular CLP pointer permissions #6352. Thanks to Old Grandpa
• FIX: Add missing colon for customPages #6393. Thanks to Jerome De Leon
• NEW: afterLogin cloud code hook #6387. Thanks to David Corona
• FIX: BREAKING CHANGE Prevent new usernames or emails that clash with existing users' email or username if it only differs by case. For example, don't allow a new user with the name 'Jane' if we already have a user 'jane'. #5634. Thanks to Arthur Cinader
• FIX: Support Travis CI V2. #6414. Thanks to Diamond Lewis

Commits

• b9742b6 Prep 4.1 (#6462)
• 3a3a5ee Merge pull request from GHSA-h4mf-75hf-67w4
• bde8ab6 Attempt to get Travis to deploy to npmjs (#6457)
• cfb0327 Update bcrypt to the latest version 🚀 (#6456)
• cd06a02 skip cleanup so we don't erase babel and stuff (#6452)
• 2a5c306 Update flow-bin to the latest version 🚀 (#6448)
• c973356 Update lint-staged to the latest version 🚀 (#6446)
• 6b0efae Do not allow to protect default fields (#6439)
• 4291f2b Prepare for 4.0 Release (#6412)
• 5947fc3 Update babel7 to the latest version 🚀 (#6450)
• Additional commits viewable in compare view

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 You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/SashiDo/content-moderation-image-api/network/alerts).

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.