refactor: Bump express-rate-limit from 8.3.0 to 8.3.1

[mtrezza]

Closes #10356

Changes

• 8.3.1: Patch release with minor fixes.

Breaking Changes

None

Code Changes Required

None — the upgrade is a drop-in replacement.

Summary by CodeRabbit

• Chores
  • Updated express-rate-limit to version 8.3.1.

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

• Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
• Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
• Group code into logical blocks. Add a short comment before each block to explain its purpose.
• We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
• Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
• Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement.

[parseplatformorg]

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

Status	Scan Engine	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

Patch version bump of express-rate-limit from 8.3.0 to 8.3.1, updating the package manifest and corresponding lockfile entries with new tarball URL and integrity hash.

Changes

Cohort / File(s)	Summary
Dependency Version Update package.json, package-lock.json	Bumped express-rate-limit from 8.3.0 to 8.3.1 with updated lockfile integrity hash and tarball URL.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• refactor: Bump express-rate-limit from 8.2.1 to 8.3.0 #10292: Earlier patch that upgraded express-rate-limit from 8.2.1 to 8.3.0; this PR continues the patch series to 8.3.1.
• refactor: Bump express-rate-limit from 7.5.1 to 8.2.1 #10046: Updates the same express-rate-limit dependency in package.json/package-lock.
• refactor: Upgrade express-rate-limit from 7.5.0 to 7.5.1 #9824: Related dependency version patch bump for express-rate-limit in package.json.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: bumping express-rate-limit from 8.3.0 to 8.3.1, which matches the file changes.
Description check	✅ Passed	The description provides the issue reference, clear explanation of changes, notes on breaking changes and code requirements, but lacks the formal sections from the repository template.
Linked Issues check	✅ Passed	The PR fully addresses issue #10356 by upgrading express-rate-limit from 8.3.0 to 8.3.1, a patch release with no functional changes required.
Out of Scope Changes check	✅ Passed	All changes are limited to dependency updates in package.json and package-lock.json, which directly align with the stated objective of upgrading express-rate-limit.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Checkov (3.2.510)

package.json

2026-03-30 17:36:13,908 [MainThread ] [ERROR] Template file not found: package.json
2026-03-30 17:36:13,916 [MainThread ] [ERROR] Template file not found: package.json
2026-03-30 17:36:13,926 [MainThread ] [ERROR] Template file not found: package.json
2026-03-30 17:36:14,021 [MainThread ] [ERROR] Failed to invoke function /usr/local/lib/python3.11/dist-packages/checkov/common/runners/object_runner. with package.json
Traceback (most recent call last):
File "/usr/local/lib/python3.11/dist-packages/checkov/common/parallelizer/parallel_runner.py", line 88, in func_wrapper
result = original_func(item)
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/checkov/common/runners/object_runner.py", line 74, in
results = parallel_runner.run_function(lambda f: (f, self._parse_file(f)), files_to_load)
^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/checkov/ope

... [truncated 2547 characters] ...

[MainThread ] [WARNI] Secret scanning: could not process file package.json
2026-03-30 17:36:14,171 [MainThread ] [ERROR] Exception traceback:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/dist-packages/checkov/main.py", line 647, in run
self.scan_reports = runner_registry.run(
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/checkov/common/runners/runner_registry.py", line 177, in run
for result in parallel_runner_results:
File "/usr/local/lib/python3.11/dist-packages/checkov/common/parallelizer/parallel_runner.py", line 118, in _run_function_multiprocess_fork
raise v.internal_exception.with_traceback(v.internal_exception.traceback)
FileNotFoundError: [Errno 2] No such file or directory: 'package.json'

---

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]

🧹 Nitpick comments (1)

package-lock.json (1)

24-24: Consider adjusting the PR title prefix.

The current PR title uses refactor: prefix, but dependency updates are typically categorized as chore: in Angular commit conventions. Consider updating the title to:

chore(deps): Bump express-rate-limit from 8.3.0 to 8.3.1

This better reflects that this is a maintenance task (dependency update) rather than a code refactor. Based on learnings, Parse Server PRs should use Angular-style titles that make meaningful changelog entries for developers.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package-lock.json` at line 24, The PR title prefix should be changed from
"refactor:" to the Angular-style "chore(deps):" to reflect a dependency update;
update the PR title to something like "chore(deps): Bump express-rate-limit from
8.3.0 to 8.3.1" so it correctly references the dependency update
(express-rate-limit) and will produce the proper changelog classification.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@package-lock.json`:
- Line 24: The PR title prefix should be changed from "refactor:" to the
Angular-style "chore(deps):" to reflect a dependency update; update the PR title
to something like "chore(deps): Bump express-rate-limit from 8.3.0 to 8.3.1" so
it correctly references the dependency update (express-rate-limit) and will
produce the proper changelog classification.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0fcb3869-ea5f-4e15-bf6b-82909c65140a

📥 Commits

Reviewing files that changed from the base of the PR and between 2f2c548 and ec47f64.

📒 Files selected for processing (2)

• package-lock.json
• package.json

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.53%. Comparing base (2f2c548) to head (ec47f64).
⚠️ Report is 4 commits behind head on alpha.

Additional details and impacted files

@@            Coverage Diff             @@
##            alpha   #10359      +/-   ##
==========================================
+ Coverage   92.52%   92.53%   +0.01%     
==========================================
  Files         192      192              
  Lines       16554    16554              
  Branches      231      231              
==========================================
+ Hits        15316    15318       +2     
+ Misses       1216     1214       -2     
  Partials       22       22              

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

[parseplatformorg]

🎉 This change has been released in version 9.7.1-alpha.1