Skip to content

refactor: Bump parse from 7.1.2 to 8.5.0#3295

Merged
mtrezza merged 2 commits intoparse-community:alphafrom
mtrezza:refactor/parse-8.5.0
Mar 31, 2026
Merged

refactor: Bump parse from 7.1.2 to 8.5.0#3295
mtrezza merged 2 commits intoparse-community:alphafrom
mtrezza:refactor/parse-8.5.0

Conversation

@mtrezza
Copy link
Copy Markdown
Member

@mtrezza mtrezza commented Mar 31, 2026

Closes #3291

Changes

  • 8.0.0: Node.js minimum version increased to >=20.19.0, >=22.12.0, >=24.1.0; security upgrade for jws dependency
  • 8.0.1-8.0.3: TypeScript type fixes for parse/node and parse/react-native subpaths
  • 8.1.0: LiveQuerySubscription.find(); ws package React-Native build fix
  • 8.2.0: createWithoutData subclass fix, Query.and/or/nor types, file upload as binary data
  • 8.3.0-8.5.0: Parse.File directory, metadata, tags, and maxUploadSize options

Breaking Changes

  • Node.js minimum version increased: >=20.19.0, >=22.12.0, >=24.1.0 (updated engines.node accordingly)

Code Changes Required

  • Updated engines.node in package.json to match new minimum versions

Summary by CodeRabbit

  • Chores
    • Upgraded the Parse library to v8.5.0.
    • Tightened Node.js engine requirements—minimum patch levels raised for supported Node 20 and 24 releases (22.x unchanged).
    • CI Node matrix updated to reflect the new Node patch thresholds.

@parse-github-assistant
Copy link
Copy Markdown

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

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 31, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6e91d967-44f3-4740-bd32-26a757b662f6

📥 Commits

Reviewing files that changed from the base of the PR and between 5427d27 and d85f338.

📒 Files selected for processing (1)
  • .github/workflows/ci.yml
✅ Files skipped from review due to trivial changes (1)
  • .github/workflows/ci.yml

📝 Walkthrough

Walkthrough

Upgrades top-level dependency parse from 7.1.2 → 8.5.0, tightens Node engine patch ranges, updates the lockfile (transitive bumps like @babel/runtime* and ws), and removes a nested parse instance under parse-server so parse-server uses the top-level parse.

Changes

Cohort / File(s) Summary
Package manifests & lockfile
package.json, package-lock.json
Bump parse 7.1.2 → 8.5.0; adjust engines.node patch minima (20.18.0→20.19.0, 24.0.0→24.1.0). Lockfile updated: transitive changes (@babel/runtime-corejs3 → 7.29.0, add @babel/runtime 7.28.6, ws 8.18.3→8.19.0), and nested parse under parse-server removed/flattened.
CI workflow
.github/workflows/ci.yml
Node matrix versions updated for check-build: NODE_VERSION for Node 20 set to 20.19.0 and for Node 24 set to 24.1.0 (no job/step changes).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 6 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Engage In Review Feedback ❓ Inconclusive GitHub PR review comments cannot be verified from git history alone; the repository shows a single commit with no iterative changes, but PR discussion data is inaccessible. Access GitHub PR #3295 directly to verify if review comments exist and whether the author addressed any feedback or engaged in discussion.
✅ Passed checks (6 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: upgrading the parse dependency from 7.1.2 to 8.5.0, matching the PR's primary objective.
Description check ✅ Passed The description includes issue reference (#3291), change details with version highlights, breaking changes, and required code changes, addressing most template elements.
Linked Issues check ✅ Passed All objectives from #3291 are addressed: parse dependency bumped to 8.5.0, engines.node constraints updated to reflect new minimums, and CI node matrix updated accordingly.
Out of Scope Changes check ✅ Passed All changes (parse version bump, engines.node updates, CI node matrix alignment) are directly related to #3291 with no out-of-scope modifications.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check ✅ Passed Parse SDK upgraded from 7.1.2 to 8.5.0 with documented security updates for jws dependency and Node.js minimum versions increased for upstream security alignment.

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

🔧 actionlint (1.7.11)
.github/workflows/ci.yml

could not read ".github/workflows/ci.yml": open .github/workflows/ci.yml: no such file or directory

🔧 YAMLlint (1.38.0)
.github/workflows/ci.yml

[Errno 2] No such file or directory: '.github/workflows/ci.yml'

🔧 Checkov (3.2.510)
.github/workflows/ci.yml

2026-03-31 16:37:11,305 [MainThread ] [ERROR] Template file not found: .github/workflows/ci.yml
2026-03-31 16:37:11,312 [MainThread ] [ERROR] Template file not found: .github/workflows/ci.yml
2026-03-31 16:37:11,363 [MainThread ] [ERROR] Template file not found: .github/workflows/ci.yml
2026-03-31 16:37:11,371 [MainThread ] [ERROR] Failed to invoke function /usr/local/lib/python3.11/dist-packages/checkov/common/runners/object_runner. with .github/workflows/ci.yml
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 "/us

... [truncated 8994 characters] ...

tem)
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/checkov/common/runners/runner_registry.py", line 839, in _parallel_run
report = runner.run(
^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/checkov/common/runners/object_runner.py", line 131, in run
self._load_files(files)
File "/usr/local/lib/python3.11/dist-packages/checkov/common/runners/object_runner.py", line 75, in _load_files
for file_result_pair in 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: '.github/workflows/ci.yml'


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

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

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@package.json`:
- Line 155: CI node matrix mismatches the package.json engines.node range—update
the Node versions tested in .github/workflows/ci.yml so they meet the engine
floors in package.json ("node": ">=20.19.0 <21.0.0 || >=22.12.0 <23.0.0 ||
>=24.1.0 <25.0.0"); replace any occurrences of 20.18.0 with 20.19.0 and 24.0.0
with 24.1.0 (or add those higher-minor versions to the matrix) in the
matrix/strategy entries (look for node-version keys or the matrix 'node' list)
so CI installs a Node that satisfies engines.node.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2b0c5cf6-0029-4a1b-a777-3d1b89a446b5

📥 Commits

Reviewing files that changed from the base of the PR and between aa1d94b and 5427d27.

📒 Files selected for processing (2)
  • package-lock.json
  • package.json

Comment thread package.json
@mtrezza mtrezza merged commit 7b8ba05 into parse-community:alpha Mar 31, 2026
11 checks passed
@mtrezza mtrezza deleted the refactor/parse-8.5.0 branch March 31, 2026 16:46
@parseplatformorg
Copy link
Copy Markdown
Contributor

🎉 This change has been released in version 9.1.0-alpha.12

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label Apr 7, 2026
@parseplatformorg
Copy link
Copy Markdown
Contributor

🎉 This change has been released in version 9.1.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label Apr 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

state:released Released as stable version state:released-alpha Released as alpha version

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants