feat: Upgrade mongodb from 6.20.0 to 7.0.0

[dependabot]

Bumps mongodb from 6.20.0 to 7.0.0.

Release notes

Sourced from mongodb's releases.

v7.0.0

7.0.0 (2025-11-06)

The MongoDB Node.js team is pleased to announce version 7.0.0 of the mongodb package!

Release Notes

The following is a detailed collection of the changes in the major v7 release of the mongodb package for Node.js. The main focus of this release was usability improvements and a streamlined API. Read on for details!

[!IMPORTANT] This is a list of changes relative to v6.21.0 of the driver. ALL changes listed below are BREAKING unless indicated otherwise. Users migrating from an older version of the driver are advised to upgrade to at least v6.21.0 before adopting v7.

🛠️ Runtime and dependency updates

Minimum Node.js version is now v20.19.0

The minimum supported Node.js version is now v20.19.0 and our TypeScript target has been updated to ES2023. We strive to keep our minimum supported Node.js version in sync with the runtime's release cadence to keep up with the latest security updates and modern language features.

Notably, the driver now offers native support for explicit resource management. Symbol.asyncDispose implementations are available on the MongoClient, ClientSession, ChangeStream and on cursors.

[!Note] Explicit resource management is considered experimental in the driver and will be until the TC39 explicit resource management proposal is completed.

bson and mongodb-connection-string-url versions 7.0.0

This driver version has been updated to use [email protected] and [email protected], which match the driver's Node.js runtime version support. BSON functionality re-exported from the driver is furthermore subject to the changes outlined in the BSON V7 release notes.

Optional peer dependency releases and version bumps

• @mongodb-js/zstd optional peer dependency minimum version raised to 7.0.0, dropped support for 1.x and 2.x (note that @mongodb-js/zstd does not have 3.x-6.x version releases)
• kerberos optional peer dependency minimum version raised to 7.0.0, dropped support for 2.x (note that kerberos does not have 3.x-6.x version releases)
• mongodb-client-encryption optional peer dependency minimum version raised to 7.0.0, dropped support for 6.x

Additionally, the driver is now compatible with the following packages:

Dependency	Previous Range	New Allowed Range
@​aws-sdk/credential-providers	^3.188.0	^3.806.0
gcp-metadata	^5.2.0	^7.0.1
socks	^2.7.1	^2.8.6

🔐 AWS authentication

To improve long-term maintainability and ensure compatibility with AWS updates, we’ve standardized AWS auth to use the official SDK in all cases and made a number of supporting changes outlined below.

@aws-sdk/credential-providers is now required for MONGODB-AWS authentication

Previous versions of the driver contained two implementations for AWS authentication and could run the risk of the custom driver implementation not supporting all AWS authentication features as well as not being correct when AWS makes changes. Using the official AWS SDK in all cases alleviates these issues.

... (truncated)

Changelog

Sourced from mongodb's changelog.

7.0.0 (2025-11-06)

⚠ BREAKING CHANGES

• NODE-7259: use alphas of all supporting packages (#4746)
• NODE-5510: dont filter change stream options (#4723)
• NODE-6296: remove cursor default batch size of 1000 (#4729)
• NODE-7150: update peer dependency matrix for 3rd party peer deps (#4720)
• NODE-7046: remove AWS uri/options support (#4689)
• NODE-4808: remove support for stream() transform on cursors and change streams (#4728)
• NODE-6377: remove noResponse option (#4724)
• NODE-6473: remove MONGODB-CR auth (#4717)
• NODE-5994: Remove metadata-related properties from public driver API (#4716)
• NODE-7016: remove beta namespace and move resource management into driver (#4719)
• NODE-4184: don't throw on aggregate with write concern and explain (#4718)
• NODE-7043, NODE-7217: adopt mongodb-client-encryption v7 (#4705)
• NODE-6065: throw MongoRuntimeError instead of MissingDependencyError in crypto connection (#4711)
• NODE-6584: improve typing for filepaths in AutoEncryptionOptions (#4341)
• NODE-6334: rename PoolRequstedRetry to PoolRequestedRetry (#4696)
• NODE-7174: drop support for Node16 and Node18 (#4668)
• NODE-7047: use custom credential provider first after URI (#4656)
• NODE-6988: require aws sdk for aws auth (#4659)

Features

• bump bson to 7.0.0-alpha.2 (#4756) (9b34953)
• NODE-4184: don't throw on aggregate with write concern and explain (#4718) (88e02a4)
• NODE-4243: drop collection checks ns not found (#4742) (a8d7c5f)
• NODE-4808: remove support for stream() transform on cursors and change streams (#4728) (1702987)
• NODE-5510: dont filter change stream options (#4723) (a2daf76)
• NODE-5545: remove deprecated objects (#4704) (cfbada6)
• NODE-5994: Remove metadata-related properties from public driver API (#4716) (b59c5ce)
• NODE-6065: throw MongoRuntimeError instead of MissingDependencyError in crypto connection (#4711) (ff229fa)
• NODE-6296: remove cursor default batch size of 1000 (#4729) (f8a855f)
• NODE-6334: rename PoolRequstedRetry to PoolRequestedRetry (#4696) (84db848)
• NODE-6377: remove noResponse option (#4724) (9e9059a)
• NODE-6473: remove MONGODB-CR auth (#4717) (9a1bc65)
• NODE-6584: improve typing for filepaths in AutoEncryptionOptions (#4341) (dab4c7c)
• NODE-6988: require aws sdk for aws auth (#4659) (b7c6750)
• NODE-7016: remove beta namespace and move resource management into driver (#4719) (fb2824f)
• NODE-7043, NODE-7217: adopt mongodb-client-encryption v7 (#4705) (3f7196e)
• NODE-7046: remove AWS uri/options support (#4689) (d14ac3f)
• NODE-7047: use custom credential provider first after URI (#4656) (2a47bbb)
• NODE-7150: update peer dependency matrix for 3rd party peer deps (#4720) (0451dae)
• NODE-7174: drop support for Node16 and Node18 (#4668) (a576b7d)
• NODE-7223: run checkout on connect regardless of credentials (#4715) (c5f74ab)
• NODE-7259: use alphas of all supporting packages (#4746) (e1ea14c)
• NODE-7260: update bson alpha to latest (#4748) (4e88559)

... (truncated)

Commits

• 2512137 chore(main): release 7.0.0 (#4667)
• e4881f5 docs(NODE-7172): create v7 migration guide (#4751)
• 53a4fb1 docs: 6.21 docs (#4782)
• 696664c feat!(NODE-7286): update peer dependencies (#4780)
• 517da84 docs: add info about testing with different versions and the rosetta setup fo...
• 252dab8 test(NODE-7219): remove unused tests (#4767)
• 76c98bb test(NODE-5206): fix flaky sdam prose test (#4752)
• cb522bf fix(NODE-7247): clarify #rewrapManyDataKey() parameter types (#4760)
• ec996e6 chore(NODE-6945): remove dependency on v8-heapsnapshot (#4763)
• 7d879fd test(NODE-7280): remove test/mongodb.ts and its usage (#4766)
• 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 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)

[parse-github-assistant]

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

[parseplatformorg]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[mtrezza]

@coderabbitai check whether this upgrade contains any breaking changes for parse-server

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

@mtrezza I'll analyze the MongoDB v7.0.0 upgrade for breaking changes that could affect parse-server.

---

🏁 Script executed:

#!/bin/bash

echo "=== Checking Node.js version requirements in package.json ==="
cat package.json | jq '.engines'

echo -e "\n=== Checking for MongoDB cursor usage patterns ==="
rg -n -C2 'cursor\.(stream|batchSize)' --type=js

echo -e "\n=== Checking for MONGODB-CR auth usage ==="
rg -n 'MONGODB-CR' --type=js

echo -e "\n=== Checking for AWS authentication usage ==="
rg -n -C2 '@aws-sdk|aws.*auth|MONGODB-AWS' --type=js

echo -e "\n=== Checking for noResponse option usage ==="
rg -n 'noResponse' --type=js

echo -e "\n=== Checking MongoDB driver import and usage patterns ==="
rg -n -C2 'from ["\x27]mongodb["\x27]|require\(["\x27]mongodb["\x27]\)' --type=js | head -50

echo -e "\n=== Checking for stream() method usage on cursors ==="
rg -n '\.stream\(' --type=js | grep -i cursor | head -20

Length of output: 3683

---

🏁 Script executed:

#!/bin/bash

echo "=== Checking for change stream usage ==="
rg -n -C3 'watch\(|ChangeStream' --type=js | head -40

echo -e "\n=== Checking for beta namespace usage ==="
rg -n 'beta\.' --type=js

echo -e "\n=== Checking for aggregate with writeConcern and explain ==="
rg -n -C2 'aggregate.*writeConcern|writeConcern.*aggregate' --type=js

echo -e "\n=== Checking for metadata-related properties ==="
rg -n 'topology|bson\.serialize|bson\.deserialize' --type=js | head -30

echo -e "\n=== Checking peer dependencies for optional MongoDB packages ==="
cat package.json | jq '.dependencies, .optionalDependencies, .peerDependencies' | grep -i 'mongodb\|bson\|@aws-sdk\|kerberos\|zstd'

echo -e "\n=== Checking current BSON and MongoDB versions ==="
cat package.json | jq '.dependencies | {"mongodb": .mongodb, "bson": .bson}'

Length of output: 4072

---

🏁 Script executed:

#!/bin/bash

echo "=== Checking for separate BSON imports ==="
rg -n 'from ["\x27]bson["\x27]|require\(["\x27]bson["\x27]\)' --type=js

echo -e "\n=== Checking MongoDB collection.watch() usage details ==="
rg -n -B5 -A10 '_mongoCollection\.watch\(' --type=js

echo -e "\n=== Checking for ObjectId and other BSON type usage ==="
rg -n 'mongodb\.ObjectId|mongodb\.Binary|mongodb\.Decimal128|mongodb\.Long' --type=js | head -30

echo -e "\n=== Checking the beta.id reference in test ==="
rg -n -B5 -A5 'beta\.id' spec/ParseAPI.spec.js

echo -e "\n=== Checking for any cursor batch size configuration ==="
rg -n -C3 'batchSize|batch' --type=js | grep -i cursor | head -20

Length of output: 2701

---

@mtrezza I've completed a thorough analysis of the MongoDB v7.0.0 upgrade for parse-server. Good news: No breaking changes should affect parse-server. Here's my detailed assessment:

✅ Compatible Changes

Node.js Version Requirements: MongoDB v7 requires Node.js >= v20.19.0, and parse-server already has this requirement, so you're fully aligned.

No Deprecated Features Used:

• ❌ MONGODB-CR authentication - Not used in parse-server
• ❌ AWS authentication features - Not used in parse-server
• ❌ noResponse option - Not used in parse-server
• ❌ .stream() method on cursors - Not used in parse-server
• ❌ Beta namespace - Not used in parse-server

Change Streams: Parse-server uses collection.watch() for schema change detection, which is standard API and fully compatible with v7.

BSON Types: Parse-server's usage of mongodb.Long and mongodb.Binary continues to work without issues.

⚠️ Notable Change (Performance Impact Only)

Cursor Batch Size:

• MongoDB v6 driver: Had a default batch size of 1000
• MongoDB v7 driver: Removed the driver default, now uses MongoDB server defaults - 101 documents for initial batch, unlimited for subsequent batches (up to 16 MiB)

Parse-server doesn't explicitly configure batch sizes, so it will now use the server defaults. The driver's 1000 default was actually causing performance overhead, so this change may actually improve performance rather than degrade it.

Summary

The MongoDB v7.0.0 upgrade is safe to proceed with no breaking changes for parse-server. The cursor batch size change should have neutral to positive performance impact.

---

🧠 Learnings used

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-12-02T08:00:20.138Z
Learning: For Parse Server 9 release (PR `#9938` and related), the parse/push-adapter dependency must be upgraded to version >= 8.0.0, not 7.0.0. Version 8.x drops support for Node 18.

---

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-12-02T08:00:08.440Z
Learning: For Parse Server 9 release preparation, the parse/push-adapter dependency should be upgraded to version >= 8.0.0, not 7.x, as version 8.x is required despite dropping Node 18 support (which aligns with Parse Server 9's removal of EOL Node versions).

---

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-11-08T13:46:04.940Z
Learning: When reviewing Parse Server PRs that add new features, always check whether the feature is documented in the README.md file, though for new Parse Server options this is optional rather than required.

---

Learnt from: EmpiDev
Repo: parse-community/parse-server PR: 9770
File: src/triggers.js:446-454
Timestamp: 2025-08-27T09:08:34.252Z
Learning: When analyzing function signature changes in Parse Server codebase, verify that call sites are actually incorrect before flagging them. Passing tests are a strong indicator that function calls are already properly aligned with new signatures.

---

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-11-17T15:02:48.786Z
Learning: For Parse Server PRs, always suggest an Angular commit convention PR title that would make a meaningful changelog entry for developers. Update the PR title suggestion on every commit. The format should be: type(scope): description. Common types include feat, fix, perf, refactor, docs, test, chore. The scope should identify the subsystem (e.g., graphql, rest, push, security). The description should be action-oriented and clearly convey the change's impact to developers.

---

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-11-17T15:02:24.824Z
Learning: For Parse Server PRs, always suggest an Angular-style PR title that would make a meaningful changelog entry for developers. Update the PR title suggestion with every new commit to the PR.

---

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 9445
File: spec/ParseLiveQuery.spec.js:1312-1338
Timestamp: 2025-05-04T20:41:05.147Z
Learning: New tests in the parse-server repository should use async/await with promise-based patterns rather than callback patterns with `done()`.

---

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-11-08T13:46:04.940Z
Learning: For new Parse Server options, verify that the option is documented in src/Options/index.js and that npm run definitions has been executed to reflect changes in src/Options/docs.js and src/Options/Definitions.js. README.md documentation is a bonus but not required for new options.

---

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 9445
File: spec/ParseLiveQuery.spec.js:1340-1375
Timestamp: 2025-05-09T09:59:06.289Z
Learning: New tests in the parse-server repository should use async/await with promise-based patterns rather than callback patterns with `done()`. The preferred pattern is to create a Promise that resolves when an expected event occurs, then await that Promise.

---

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-12-02T06:55:53.808Z
Learning: When reviewing Parse Server PRs that add or modify Parse Server options, always verify that changes are properly reflected in three files: src/Options/index.js (where changes originate), src/Options/Definitions.js, and src/Options/docs.js. The correct workflow is: make changes in index.js first, then run `npm run definitions` to automatically replicate the changes to Definitions.js and docs.js.

[mtrezza]

@coderabbitai which APIs in parse-server could be affected by the change in cursor batch size?

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash

echo "=== Finding all MongoDB cursor usage in parse-server ==="
rg -n -C3 '\.find\(|\.aggregate\(|cursor' --type=js src/ | head -100

echo -e "\n=== Checking for explicit batch size configurations ==="
rg -n -C3 'batchSize' --type=js src/

echo -e "\n=== Finding large result set query patterns ==="
rg -n -C3 '\.toArray\(\)|\.forEach\(|\.map\(' --type=js src/ | head -100

echo -e "\n=== Checking REST API query endpoints ==="
rg -n -C5 'class.*Controller|export.*function.*find|export.*function.*query' --type=js src/Controllers/ | head -80

echo -e "\n=== Checking GraphQL query operations ==="
rg -n -C3 'find.*objects|query.*objects' --type=js src/GraphQL/ | head -50

echo -e "\n=== Checking LiveQuery subscription patterns ==="
rg -n -C3 'subscription|matchesQuery' --type=js src/LiveQuery/ | head -50

Length of output: 21745

---

🏁 Script executed:

#!/bin/bash

echo "=== Checking REST Query implementation and limit handling ==="
rg -n -C5 'class RestQuery|executeFind|buildRestWhere' --type=js src/RestQuery.js | head -80

echo -e "\n=== Checking database adapter find operations ==="
rg -n -C3 'adaptiveCollection\.find|rawFind' --type=js src/Adapters/ | head -60

echo -e "\n=== Checking aggregate operations ==="
rg -n -C5 'aggregate\(' --type=js src/ | head -80

echo -e "\n=== Checking for scan/export operations ==="
rg -n -C3 'export|scan.*collection|getAllClasses' --type=js src/ | head -50

echo -e "\n=== Checking default limit configurations ==="
rg -n 'defaultLimit|maxLimit|MAX.*LIMIT' --type=js src/ | head -40

echo -e "\n=== Checking Push notification query patterns ==="
cat src/Push/PushQueue.js | head -60

Length of output: 15468

---

@mtrezza Based on my analysis of the parse-server codebase, here are the APIs that could be affected by the MongoDB v7 cursor batch size change:

✅ Minimal Impact APIs (Protected by Explicit Limits)

REST API Queries (GET /classes/:className, /users, /roles, etc.):

• Not significantly affected - These use defaultLimit: 100 and respect maxLimit configuration
• Limits are applied before cursor iteration via ClassesRouter.optionsFromBody()

GraphQL Queries:

• Not significantly affected - Limit/skip handled by objectsQueries helper
• Respects maxLimit configuration (Lines 157-159 in GraphQL/helpers/objectsQueries.js)

Push Notifications:

• Not affected - Uses application-level batching (DEFAULT_BATCH_SIZE: 100)
• Queries _Installation with explicit limit: 100 and skip pagination

⚠️ Potentially Affected APIs

1. Aggregation API (POST /aggregate/:className):

• Could be affected for large result sets
• Uses collection.aggregate(pipeline).toArray() without explicit batch size
• No cursor-level limits applied - returns entire aggregation result
• Impact: Network efficiency could change for aggregations returning thousands of documents

2. Internal Schema Operations:

• _fetchAllSchemasFrom_SCHEMA() uses _rawFind({}) with no limit
• Low practical impact - _SCHEMA collection typically has <100 entries
• Only runs during schema reloads

3. Background/Administrative Operations:

• Schema migration scans
• Configuration queries (GlobalConfig with limit: 1 - not affected)
• Validation queries (typically single-document lookups - not affected)

Summary

The MongoDB v7 cursor batch size change should have minimal impact on parse-server because:

1. Most user-facing APIs already enforce limits (default: 100, configurable via maxLimit)
2. The aggregation API is the primary area where large result sets could be affected
3. Internal operations mostly query small collections or use explicit limits

The change from driver's 1000 default to server's 101 initial/unlimited subsequent batches will primarily affect aggregation queries that return large result sets. For typical parse-server usage patterns with pagination, the impact should be neutral to positive in terms of performance.

Recommendation: Monitor aggregation query performance after upgrading, especially for operations that return large result sets (>1000 documents).

---

🧠 Learnings used

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-12-02T08:00:20.138Z
Learning: For Parse Server 9 release (PR `#9938` and related), the parse/push-adapter dependency must be upgraded to version >= 8.0.0, not 7.0.0. Version 8.x drops support for Node 18.

---

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-12-02T08:00:08.440Z
Learning: For Parse Server 9 release preparation, the parse/push-adapter dependency should be upgraded to version >= 8.0.0, not 7.x, as version 8.x is required despite dropping Node 18 support (which aligns with Parse Server 9's removal of EOL Node versions).

---

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-11-08T13:46:04.940Z
Learning: When reviewing Parse Server PRs that add new features, always check whether the feature is documented in the README.md file, though for new Parse Server options this is optional rather than required.

---

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-12-02T06:55:53.808Z
Learning: When reviewing Parse Server PRs that add or modify Parse Server options, always verify that changes are properly reflected in three files: src/Options/index.js (where changes originate), src/Options/Definitions.js, and src/Options/docs.js. The correct workflow is: make changes in index.js first, then run `npm run definitions` to automatically replicate the changes to Definitions.js and docs.js.

---

Learnt from: EmpiDev
Repo: parse-community/parse-server PR: 9770
File: src/triggers.js:446-454
Timestamp: 2025-08-27T09:08:34.252Z
Learning: When analyzing function signature changes in Parse Server codebase, verify that call sites are actually incorrect before flagging them. Passing tests are a strong indicator that function calls are already properly aligned with new signatures.

---

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-11-08T13:46:04.940Z
Learning: For new Parse Server options, verify that the option is documented in src/Options/index.js and that npm run definitions has been executed to reflect changes in src/Options/docs.js and src/Options/Definitions.js. README.md documentation is a bonus but not required for new options.

---

Learnt from: EmpiDev
Repo: parse-community/parse-server PR: 9770
File: src/triggers.js:467-477
Timestamp: 2025-08-27T12:33:06.237Z
Learning: In the Parse Server codebase, maybeRunAfterFindTrigger is called in production with Parse.Query objects constructed via withJSON(), so the plain object query handling bug only affects tests, not production code paths.

---

Learnt from: RahulLanjewar93
Repo: parse-community/parse-server PR: 9744
File: spec/ParseLiveQuery.spec.js:0-0
Timestamp: 2025-04-30T19:31:35.344Z
Learning: In the Parse Server codebase, the functions in QueryTools.js are typically tested through end-to-end behavior tests rather than direct unit tests, even though the functions are exported from the module.

---

Learnt from: mtrezza
Repo: parse-community/parse-server PR: 0
File: :0-0
Timestamp: 2025-11-17T15:02:48.786Z
Learning: For Parse Server PRs, always suggest an Angular commit convention PR title that would make a meaningful changelog entry for developers. Update the PR title suggestion on every commit. The format should be: type(scope): description. Common types include feat, fix, perf, refactor, docs, test, chore. The scope should identify the subsystem (e.g., graphql, rest, push, security). The description should be action-oriented and clearly convey the change's impact to developers.

---

Learnt from: EmpiDev
Repo: parse-community/parse-server PR: 9770
File: spec/CloudCode.spec.js:446-469
Timestamp: 2025-08-26T14:06:31.853Z
Learning: In the Parse Server codebase, when handling query objects in maybeRunAfterFindTrigger, objects without a where property that contain options like limit/skip should be treated as query JSON with an empty where clause using the spread pattern { where: {}, ...query }, not nested as { where: query }.

[parse-github-assistant]

🚀 Thanks for opening this pull request!

[parseplatformorg]

🎉 This change has been released in version 9.2.0-alpha.4