feat: Upgrade to parse 7.1.1

[mtrezza]

Summary by CodeRabbit

• Chores
  • Updated an internal dependency and reordered development-only dependency entries (non-functional).

---

Note: This release contains no user-facing changes. Updates are maintenance-related only.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[parse-github-assistant]

🚀 Thanks for opening this pull request!

[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]

📝 Walkthrough

Walkthrough

package.json updated: the parse dependency was bumped from 7.0.1 to 7.1.1, and @babel/eslint-parser was reordered within devDependencies without a version change (7.28.0).

Changes

Cohort / File(s)	Change Summary
Dependency updates package.json	Bumped parse from 7.0.1 → 7.1.1; moved/reordered @babel/eslint-parser within devDependencies (version remains 7.28.0).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

• Check compatibility of parse@7.1.1 with existing code and tests.
• Confirm @babel/eslint-parser reorder has no accidental side-effects in lockfile or install scripts.

Possibly related PRs

• fix: Security upgrade to parse 7.0.1 #9877 — Earlier bump to parse that this PR continues (previously upgraded to 7.0.1).

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided by the author, missing all required template sections including Issue, Approach, and Tasks.	Add a pull request description following the repository template, including linked issue, description of changes, and applicable task checkboxes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main change—upgrading the parse dependency from 7.0.1 to 7.1.1, and is clear and specific.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a906a11 and 7799bf4.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (2 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

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

📚 Learning: 2025-11-17T15:02:48.786Z

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.

Applied to files:

• package.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (14)

• GitHub Check: PostgreSQL 18, PostGIS 3.6
• GitHub Check: Node 22
• GitHub Check: Redis Cache
• GitHub Check: MongoDB 7, ReplicaSet
• GitHub Check: PostgreSQL 17, PostGIS 3.5
• GitHub Check: MongoDB 6, ReplicaSet
• GitHub Check: MongoDB 8, ReplicaSet
• GitHub Check: PostgreSQL 16, PostGIS 3.5
• GitHub Check: PostgreSQL 15, PostGIS 3.4
• GitHub Check: PostgreSQL 15, PostGIS 3.5
• GitHub Check: PostgreSQL 15, PostGIS 3.3
• GitHub Check: Docker Build
• GitHub Check: Code Analysis (javascript)
• GitHub Check: Benchmarks

🔇 Additional comments (2)

package.json (2)

71-71: Incidental devDependency reordering.

The @babel/eslint-parser is reordered to line 71 while maintaining its current version 7.28.0. This change appears to be a side effect (possibly from dependency sorting or alphabetization), but functionally has no impact.

---

1-174: PR title already follows Angular convention.

The PR title "feat: Upgrade to parse 7.1.0" already follows the Angular commit convention with type and scope implied. Once the parse version issue is resolved, this title will make a clear changelog entry for users upgrading Parse Server.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.75%. Comparing base (4752197) to head (7a4da5d).
⚠️ Report is 5 commits behind head on alpha.

Additional details and impacted files

@@            Coverage Diff             @@
##            alpha    #9954      +/-   ##
==========================================
- Coverage   93.76%   93.75%   -0.02%     
==========================================
  Files         188      188              
  Lines       15297    15297              
  Branches      177      177              
==========================================
- Hits        14343    14341       -2     
- Misses        942      944       +2     
  Partials       12       12              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 0

♻️ Duplicate comments (1)

package.json (1)

50-50: Parse package version 7.1.1 does not exist; npm install will fail.

The npm registry shows parse 6.1.1 as the latest published version (April 4, 2025). While version 7.0.2 exists on the GitHub repository (October 25, 2025), it is not available on the npm registry. Version 7.1.1 does not exist in either location.

Correct this to use a valid, published version. If you need features from 7.0.2, configure your dependency to pull directly from the GitHub repository; otherwise, use 6.1.1 or consult the team about version requirements.

🧹 Nitpick comments (1)

package.json (1)

1-174: Suggest Angular-style PR title for meaningful changelog.

Based on the learnings, update the PR title to follow Angular commit convention, which generates meaningful changelog entries for developers. The format is: type(scope): description.

Suggested title: deps(parse): upgrade to parse 7.0.2 (or the intended version once confirmed).

This ensures the change is properly documented for release notes.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7799bf4 and 7a4da5d.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (2 hunks)

🧰 Additional context used

🧠 Learnings (4)

📓 Common learnings

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

📚 Learning: 2025-11-17T15:02:48.786Z

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.

Applied to files:

• package.json

📚 Learning: 2025-11-08T13:46:04.940Z

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.

Applied to files:

• package.json

📚 Learning: 2025-11-17T15:02:24.824Z

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.

Applied to files:

• package.json

🔇 Additional comments (1)

package.json (1)

71-71: Note: @babel/eslint-parser reordering is cosmetic.

Line 71 shows @babel/eslint-parser reordered within devDependencies with no version change (7.28.0). This appears to be a stylistic change with no functional impact, but verify this was intentional rather than an accidental artifact.

[parseplatformorg]

🎉 This change has been released in version 8.5.0-alpha.17

[parseplatformorg]

🎉 This change has been released in version 8.5.0