build: Release beta #9033
Merged
build: Release beta #9033
Conversation
This file contains 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
# [6.5.0-alpha.1](parse-community/parse-server@6.4.0...6.5.0-alpha.1) (2023-11-18) ### Bug Fixes * Context not passed to Cloud Code Trigger `beforeFind` when using `Parse.Query.include` ([parse-community#8765](parse-community#8765)) ([7d32d89](parse-community@7d32d89)) * Parse Server option `fileUpload.fileExtensions` fails to determine file extension if filename contains multiple dots ([parse-community#8754](parse-community#8754)) ([3d6d50e](parse-community@3d6d50e)) * Security bump @babel/traverse from 7.20.5 to 7.23.2 ([parse-community#8777](parse-community#8777)) ([2d6b3d1](parse-community@2d6b3d1)) * Security upgrade graphql from 16.6.0 to 16.8.1 ([parse-community#8758](parse-community#8758)) ([71dfd8a](parse-community@71dfd8a)) ### Features * Add `$setOnInsert` operator to `Parse.Server.database.update` ([parse-community#8791](parse-community#8791)) ([f630a45](parse-community@f630a45)) * Add compatibility for MongoDB Atlas Serverless and AWS Amazon DocumentDB with collation options `enableCollationCaseComparison`, `transformEmailToLowercase`, `transformUsernameToLowercase` ([parse-community#8805](parse-community#8805)) ([09fbeeb](parse-community@09fbeeb)) * Add context to Cloud Code Triggers `beforeLogin` and `afterLogin` ([parse-community#8724](parse-community#8724)) ([a9c34ef](parse-community@a9c34ef)) * Allow setting `createdAt` and `updatedAt` during `Parse.Object` creation with maintenance key ([parse-community#8696](parse-community#8696)) ([77bbfb3](parse-community@77bbfb3)) * Upgrade Parse Server Push Adapter to 5.0.2 ([parse-community#8813](parse-community#8813)) ([6ef1986](parse-community@6ef1986))
# [6.5.0-alpha.2](parse-community/parse-server@6.5.0-alpha.1...6.5.0-alpha.2) (2023-11-19) ### Performance Improvements * Improved IP validation performance for `masterKeyIPs`, `maintenanceKeyIPs` ([parse-community#8510](parse-community#8510)) ([b87daba](parse-community@b87daba))
BREAKING CHANGE: `Parse.Query` no longer supports the BSON type `code`; although this feature was never officially documented, its removal is announced as a breaking change to protect deployments where it might be in use.
# [7.0.0-alpha.1](parse-community/parse-server@6.5.0-alpha.2...7.0.0-alpha.1) (2023-12-10) ### Features * Add support for MongoDB 7 ([parse-community#8761](parse-community#8761)) ([3de8494](parse-community@3de8494)) ### BREAKING CHANGES * `Parse.Query` no longer supports the BSON type `code`; although this feature was never officially documented, its removal is announced as a breaking change to protect deployments where it might be in use. ([3de8494](3de8494))
…entLoginWithUnverifiedEmail` (parse-community#8836)
# [7.0.0-alpha.2](parse-community/parse-server@7.0.0-alpha.1...7.0.0-alpha.2) (2023-12-17) ### Features * Add `installationId` to arguments for `verifyUserEmails`, `preventLoginWithUnverifiedEmail` ([parse-community#8836](parse-community#8836)) ([a22dbe1](parse-community@a22dbe1))
…of throwing error (parse-community#8722) BREAKING CHANGE: `Parse.Session.current()` no longer throws an error if the session token is expired, but instead returns the session token with its expiration date to allow checking its validity
…ifyUserEmails`, `preventLoginWithUnverifiedEmail` set to functions (parse-community#8838)
# [7.0.0-alpha.3](parse-community/parse-server@7.0.0-alpha.2...7.0.0-alpha.3) (2023-12-26) ### Bug Fixes * Conditional email verification not working in some cases if `verifyUserEmails`, `preventLoginWithUnverifiedEmail` set to functions ([parse-community#8838](parse-community#8838)) ([8e7a6b1](parse-community@8e7a6b1)) ### Features * Allow `Parse.Session.current` on expired session token instead of throwing error ([parse-community#8722](parse-community#8722)) ([f9dde4a](parse-community@f9dde4a)) ### BREAKING CHANGES * `Parse.Session.current()` no longer throws an error if the session token is expired, but instead returns the session token with its expiration date to allow checking its validity ([f9dde4a](f9dde4a))
…`verifyUserEmails`, `preventLoginWithUnverifiedEmail` on login (parse-community#8850)
# [7.0.0-alpha.4](parse-community/parse-server@7.0.0-alpha.3...7.0.0-alpha.4) (2023-12-27) ### Features * Add `Parse.User` as function parameter to Parse Server options `verifyUserEmails`, `preventLoginWithUnverifiedEmail` on login ([parse-community#8850](parse-community#8850)) ([972f630](parse-community@972f630))
… to `verifyUserEmails` on verification email request (parse-community#8873) BREAKING CHANGE: The `Parse.User` passed as argument if `verifyUserEmails` is set to a function is renamed from `user` to `object` for consistency with invocations of `verifyUserEmails` on signup or login; the user object is not a plain JavaScript object anymore but an instance of `Parse.User`
# [7.0.0-alpha.5](parse-community/parse-server@7.0.0-alpha.4...7.0.0-alpha.5) (2024-01-06) ### Features * Add `installationId`, `ip`, `resendRequest` to arguments passed to `verifyUserEmails` on verification email request ([parse-community#8873](parse-community#8873)) ([8adcbee](parse-community@8adcbee)) ### BREAKING CHANGES * The `Parse.User` passed as argument if `verifyUserEmails` is set to a function is renamed from `user` to `object` for consistency with invocations of `verifyUserEmails` on signup or login; the user object is not a plain JavaScript object anymore but an instance of `Parse.User` ([8adcbee](8adcbee))
…es new token on every email verification request (parse-community#8885)
# [7.0.0-alpha.6](parse-community/parse-server@7.0.0-alpha.5...7.0.0-alpha.6) (2024-01-14) ### Bug Fixes * Parse Server option `emailVerifyTokenReuseIfValid: true` generates new token on every email verification request ([parse-community#8885](parse-community#8885)) ([0023ce4](parse-community@0023ce4))
# [7.0.0-alpha.7](parse-community/parse-server@7.0.0-alpha.6...7.0.0-alpha.7) (2024-01-14) ### Bug Fixes * Username is `undefined` in email verification link on email change ([parse-community#8887](parse-community#8887)) ([e315c13](parse-community@e315c13))
…e and email are changed (parse-community#8889)
# [7.0.0-alpha.8](parse-community/parse-server@7.0.0-alpha.7...7.0.0-alpha.8) (2024-01-15) ### Bug Fixes * Incomplete user object in `verifyEmail` function if both username and email are changed ([parse-community#8889](parse-community#8889)) ([1eb95ae](parse-community@1eb95ae))
# [7.0.0-alpha.9](parse-community/parse-server@7.0.0-alpha.8...7.0.0-alpha.9) (2024-01-15) ### Bug Fixes * Server crashes when receiving an array of `Parse.Pointer` in the request body ([parse-community#8784](parse-community#8784)) ([66e3603](parse-community@66e3603))
…ed email using master key and option `ignoreEmailVerification` (parse-community#8895)
# [7.0.0-alpha.10](parse-community/parse-server@7.0.0-alpha.9...7.0.0-alpha.10) (2024-01-17) ### Features * Add password validation via POST request for user with unverified email using master key and option `ignoreEmailVerification` ([parse-community#8895](parse-community#8895)) ([633a9d2](parse-community@633a9d2))
BREAKING CHANGE: Removes support for Postgres 11 and 12
# [7.0.0-alpha.11](parse-community/parse-server@7.0.0-alpha.10...7.0.0-alpha.11) (2024-01-22) ### Features * Add support for Postgres 16 ([parse-community#8898](parse-community#8898)) ([99489b2](parse-community@99489b2)) ### BREAKING CHANGES * Removes support for Postgres 11 and 12 ([99489b2](99489b2))
…extensions that are less than 3 or more than 4 characters long (parse-community#8699)
# [7.0.0-alpha.26](parse-community/parse-server@7.0.0-alpha.25...7.0.0-alpha.26) (2024-03-10) ### Bug Fixes * Parse Server option `fileExtensions` default value rejects file extensions that are less than 3 or more than 4 characters long ([parse-community#8699](parse-community#8699)) ([2760381](parse-community@2760381))
# [7.0.0-alpha.27](parse-community/parse-server@7.0.0-alpha.26...7.0.0-alpha.27) (2024-03-15) ### Bug Fixes * CacheAdapter does not connect when using a CacheAdapter with a JSON config ([parse-community#8633](parse-community#8633)) ([720d24e](parse-community@720d24e))
# [7.0.0-alpha.28](parse-community/parse-server@7.0.0-alpha.27...7.0.0-alpha.28) (2024-03-17) ### Features * Upgrade to Parse JS SDK 5 ([parse-community#9022](parse-community#9022)) ([ad4aa83](parse-community@ad4aa83))
…s security vulnerability [GHSA-6hh7-46r2-vf29](GHSA-6hh7-46r2-vf29) (parse-community#9024)
# [7.0.0-alpha.29](parse-community/parse-server@7.0.0-alpha.28...7.0.0-alpha.29) (2024-03-19) ### Bug Fixes * Server crashes on invalid Cloud Function or Cloud Job name; fixes security vulnerability [GHSA-6hh7-46r2-vf29](GHSA-6hh7-46r2-vf29) ([parse-community#9024](parse-community#9024)) ([9f6e342](parse-community@9f6e342))
|
I will reformat the title to use the proper commit message syntax. |
Thanks for opening this pull request!
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## beta #9033 +/- ##
==========================================
- Coverage 94.31% 94.14% -0.17%
==========================================
Files 186 186
Lines 14798 14681 -117
==========================================
- Hits 13956 13822 -134
- Misses 842 859 +17 ☔ View full report in Codecov by Sentry. |
|
🎉 This change has been released in version 7.0.0-beta.1 |
|
🎉 This change has been released in version 7.0.0 |
|
🎉 This change has been released in version 7.0.0-alpha.30 |
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.
No description provided.