Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Upgrade to parse-server 7.2.0 #470

Merged
merged 4 commits into from
Jul 12, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 12, 2024

Bumps parse-server from 6.5.0 to 7.2.0.

Release notes

Sourced from parse-server's releases.

7.2.0

7.2.0 (2024-07-09)

Bug Fixes

  • Invalid push notification tokens are not cleaned up from database for FCM API v2 (#9173) (284da09)

Features

  • Add support for dot notation on array fields of Parse Object (#9115) (cf4c880)
  • Upgrade to @​parse/push-adapter 6.4.0 (#9182) (ef1634b)
  • Upgrade to Parse JS SDK 5.3.0 (#9180) (dca187f)

7.2.0-beta.1

7.2.0-beta.1 (2024-07-09)

Bug Fixes

  • Invalid push notification tokens are not cleaned up from database for FCM API v2 (#9173) (284da09)

Features

  • Add support for dot notation on array fields of Parse Object (#9115) (cf4c880)
  • Upgrade to @​parse/push-adapter 6.4.0 (#9182) (ef1634b)
  • Upgrade to Parse JS SDK 5.3.0 (#9180) (dca187f)

7.1.0

7.1.0 (2024-06-30)

[!WARNING] We recommend to skip this release. This release contains a bug in which a Parse Object property that is an object is converted to an array if the object's nested key name is number-like. For example, a Parse Object property that is stored in the database as object { 0: 'a' } is returned as array ['a']. The bug has been introduced via the Parse JS SDK 5.2.0 which is used in Parse Server Cloud Code. Other Parse client SDKs and the Parse Server REST API are unaffected. For more information see the release notes of Parse JS SDK 5.3.0 in which the bug has been fixed.

Bug Fixes

  • Parse.Cloud.startJob and Parse.Push.send not returning status ID when setting Parse Server option directAccess: true (#8766) (5b0efb2)
  • Required option not handled correctly for special fields (File, GeoPoint, Polygon) on GraphQL API mutations (#8915) (907ad42)
  • Facebook Limited Login not working due to incorrect domain in JWT validation (#9122) (9d0bd2b)
  • Live query throws error when constraint notEqualTo is set to null (#8835) (11d3e48)
  • Parse Server option extendSessionOnUse not working for session lengths < 24 hours (#9113) (0a054e6)
  • Rate limiting can fail when using Parse Server option rateLimit.redisUrl with clusters (#8632) (c277739)
  • SQL injection when using Parse Server with PostgreSQL; fixes security vulnerability GHSA-c2hr-cqg6-8j6r (#9167) (2edf1e4)

Features

  • Add silent log level for Cloud Code (#8803) (5f81efb)
  • Add server security check status security.enableCheck to Features Router (#8679) (b07ec15)
  • Prevent Parse Server start in case of unknown option in server configuration (#8987) (8758e6a)
  • Upgrade to @​parse/push-adapter 6.0.0 (#9066) (18bdbf8)

... (truncated)

Commits
  • 1979de0 chore(release): 7.2.0 [skip ci]
  • 6f2fc44 build: Release (#9189)
  • c696e1e empty
  • 70146bb chore(release): 7.2.0-beta.1 [skip ci]
  • 694da02 build: Release (#9186)
  • e1d4d12 Merge branch 'release' into build
  • 68922c8 refactor: Upgrade semantic release (#9185)
  • 1e21b69 test: Object data type should not change from beforeSave to afterSave tri...
  • 3353998 chore(release): 7.1.0-alpha.16 [skip ci]
  • cf4c880 feat: Add support for dot notation on array fields of Parse Object (#9115)
  • Additional commits viewable in compare view

Dependabot compatibility score

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

Bumps [parse-server](https://github.com/parse-community/parse-server) from 6.5.0 to 7.2.0.
- [Release notes](https://github.com/parse-community/parse-server/releases)
- [Changelog](https://github.com/parse-community/parse-server/blob/alpha/CHANGELOG.md)
- [Commits](parse-community/parse-server@6.5.0...7.2.0)

---
updated-dependencies:
- dependency-name: parse-server
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jul 12, 2024
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title refactor: bump parse-server from 6.5.0 to 7.2.0 refactor: Bump parse-server from 6.5.0 to 7.2.0 Jul 12, 2024
@mtrezza mtrezza changed the title refactor: Bump parse-server from 6.5.0 to 7.2.0 feat: Upgrade to parse-server 7.2.0 Jul 12, 2024
Copy link

Thanks for opening this pull request!

  • ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

@mtrezza mtrezza merged commit 49ac7b5 into master Jul 12, 2024
4 checks passed
@mtrezza mtrezza deleted the dependabot/npm_and_yarn/parse-server-7.2.0 branch July 12, 2024 22:14
parseplatformorg pushed a commit that referenced this pull request Jul 12, 2024
# [1.4.0](1.3.1...1.4.0) (2024-07-12)

### Features

* Upgrade to parse-server 7.2.0 ([#470](#470)) ([49ac7b5](49ac7b5))
parseplatformorg pushed a commit that referenced this pull request Jul 12, 2024
# [2.0.0](1.3.1...2.0.0) (2024-07-12)

### Features

* Add support for Node 20, 22; remove support for Node 14, 16 ([#473](#473)) ([9442870](9442870))
* Upgrade to parse-server 7.2.0 ([#470](#470)) ([49ac7b5](49ac7b5))

### BREAKING CHANGES

* Removes support for Node 14, 16. ([9442870](9442870))
@parseplatformorg
Copy link

🎉 This change has been released in version 2.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file state:released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants