feat: Upgrade to parse 8.2.0, @parse/push-adapter 8.3.0

[mtrezza]

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.

Issue

Upgrade to parse 8.2.0, @parse/push-adapter 8.3.0

Summary by CodeRabbit

• Chores
  • Updated dependency versions to latest releases for improved performance and stability.

[parse-github-assistant]

🚀 Thanks for opening this pull request!

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

Dependency versions updated in package.json: @parse/push-adapter from 8.2.0 to 8.3.0 and parse from 8.0.3 to 8.2.0. No changes to public entity signatures.

Changes

Cohort / File(s)	Summary
Dependency Updates package.json	Updated @parse/push-adapter to 8.3.0 and parse to 8.2.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• docs: Simplify PR template #10026: Updates @parse/push-adapter dependency to a newer version in package.json
• feat: Upgrade to parse 8.0.0 #9976: Modifies parse dependency version in package.json
• feat: Upgrade to parse 8.0.3 and @parse/push-adapter 8.2.0 #10021: Upgrades both parse and @parse/push-adapter dependencies simultaneously in package.json

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete. It only provides boilerplate content and a brief issue statement, but lacks the required 'Approach' section explaining the changes and 'Tasks' checklist.	Add an 'Approach' section describing the upgrade details and rationale, and complete the 'Tasks' checklist by checking applicable items or explicitly indicating why tasks don't apply.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and specifically describes the main change: upgrading two dependencies (parse to 8.2.0 and @parse/push-adapter to 8.3.0), which matches the pull request's core objective.
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
• 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.}

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

[parseplatformorg]

🎉 This change has been released in version 9.3.0-alpha.7

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.57%. Comparing base (4ef89d9) to head (b26a958).
⚠️ Report is 7 commits behind head on alpha.

Additional details and impacted files

@@           Coverage Diff           @@
##            alpha   #10066   +/-   ##
=======================================
  Coverage   92.57%   92.57%           
=======================================
  Files         191      191           
  Lines       15603    15603           
  Branches      176      176           
=======================================
  Hits        14445    14445           
  Misses       1146     1146           
  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.

[parseplatformorg]

🎉 This change has been released in version 9.3.0