Skip to content

feat: Upgrade to parse 8.6.0#559

Merged
mtrezza merged 1 commit intoparse-community:masterfrom
mtrezza:feat/upgrade-to-parse
Apr 17, 2026
Merged

feat: Upgrade to parse 8.6.0#559
mtrezza merged 1 commit intoparse-community:masterfrom
mtrezza:feat/upgrade-to-parse

Conversation

@mtrezza
Copy link
Copy Markdown
Member

@mtrezza mtrezza commented Apr 17, 2026

Pull Request

Issue

Upgrade to parse 8.6.0

Tasks

  • Add tests
  • Add changes to documentation (guides, repository pages, code comments)

Summary by CodeRabbit

  • Chores
    • Updated the parse library and related dependencies to the latest compatible versions for improved stability and security.

@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. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 17, 2026

Caution

Review failed

Pull request was closed or merged during review

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: b92b75d9-dacf-4637-b3ee-ace0e228e403

📥 Commits

Reviewing files that changed from the base of the PR and between 2695519 and c2620f6.

📒 Files selected for processing (2)
  • package-lock.json
  • package.json
👮 Files not reviewed due to content moderation or server errors (1)
  • package-lock.json

📝 Walkthrough

Walkthrough

A dependency version update that upgrades the parse package from 8.5.0 to 8.6.0 and updates associated transitive dependencies including @babel/runtime, core-js-pure, and ws packages, with corresponding lockfile hash and integrity value updates.

Changes

Cohort / File(s) Summary
Dependency Version Upgrade
package.json
Updated parse dependency version from 8.5.0 to 8.6.0.
Lockfile Synchronization
package-lock.json
Updated parse package to 8.6.0 with adjusted engine constraint (>=22.13.0 <23); transitive dependencies updated: @babel/runtime to 7.29.2, @babel/runtime-corejs3 to 7.29.2, core-js-pure to 3.49.0, ws to 8.20.0; all resolved tarballs, integrity hashes, and license fields synchronized.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The PR description follows the template structure but is missing the 'Approach' section that should describe the changes in detail. Add an 'Approach' section explaining the changes made, such as the dependency versions updated and any related updates to transitive dependencies.
Engage In Review Feedback ❓ Inconclusive Pull request review feedback and user engagement cannot be verified in the sandbox environment; review comments are not accessible in the git repository. Access the GitHub pull request directly to review all comments and verify whether the user has appropriately engaged with any feedback provided by reviewers.
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The PR title 'feat: Upgrade to parse 8.6.0' follows the required format with 'feat:' prefix and clearly describes the main change of upgrading the parse dependency.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Security Check ✅ Passed PR contains only dependency version updates with no application source code changes. All packages updated to newer versions with proper integrity hashes from legitimate npmjs.org sources.

✏️ 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.519)
package.json

2026-04-17 07:42:26,134 [MainThread ] [ERROR] Template file not found: package.json
2026-04-17 07:42:26,135 [MainThread ] [ERROR] Template file not found: package.json
2026-04-17 07:42:26,139 [MainThread ] [ERROR] Template file not found: package.json
2026-04-17 07:42:26,178 [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] ...

ck__)
FileNotFoundError: [Errno 2] No such file or directory: 'package.json'
2026-04-17 07:42:26,219 [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

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

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 17, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.18%. Comparing base (2695519) to head (c2620f6).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #559   +/-   ##
=======================================
  Coverage   99.18%   99.18%           
=======================================
  Files          11       11           
  Lines        1841     1841           
=======================================
  Hits         1826     1826           
  Misses         15       15           

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

@mtrezza mtrezza merged commit 4d35291 into parse-community:master Apr 17, 2026
8 of 9 checks passed
@mtrezza mtrezza deleted the feat/upgrade-to-parse branch April 17, 2026 07:44
parseplatformorg pushed a commit that referenced this pull request Apr 17, 2026
# [8.5.0](8.4.0...8.5.0) (2026-04-17)

### Features

* Upgrade to parse 8.6.0 ([#559](#559)) ([4d35291](4d35291))
@parseplatformorg
Copy link
Copy Markdown
Contributor

🎉 This change has been released in version 8.5.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants