refactor: Bump semver from 7.7.4 to 7.8.5

[mtrezza]

Issue

Closes #583

semver is out of date at 7.7.4; 7.8.5 is the current release.

Approach

Bumps the semver devDependency from 7.7.4 to 7.8.5, pinned to an exact version. Manifest and lock file only — no code changes.

Changes

• Patch and minor releases between 7.7.4 and 7.8.5 — no breaking changes, no deprecations, no API changes.

Breaking Changes

None.

Code Changes Required

None — drop-in replacement.

Tasks

• Verify CI passes on all supported Node versions

Summary by CodeRabbit

• Chores
  • Updated the development tooling’s semantic versioning package to version 7.8.5.
  • Refreshed the installed package lock data to match the updated dependency versions.

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

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Essentials

Run ID: 4b94ea92-a494-4f6d-b993-aef4d660984b

📥 Commits

Reviewing files that changed from the base of the PR and between b9245cb and b6bcfdd.

📒 Files selected for processing (2)

• package-lock.json
• package.json

Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.

---

📝 Walkthrough

Walkthrough

The project upgrades its semver development dependency from 7.7.4 to 7.8.5. The lockfile updates the root and top-level package resolutions and adds a nested parse-server semver entry at 7.7.4.

Changes

Semver upgrade

Layer / File(s)	Summary
Update semver dependency package.json, package-lock.json	The development dependency and top-level lockfile resolution change to semver 7.8.5. The lockfile also records the nested parse-server semver 7.7.4 package entry.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to b6bcf

This development dependency upgrade updates semver and its lockfile resolution without changing product behavior; the PR is ready to merge.

---

Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Engage In Review Feedback	❓ Inconclusive	The current review reports zero actionable findings, but it explicitly does not establish whether earlier review comments exist or were resolved. The available evidence cannot confirm that the contrib…	Provide the complete review-comment history, including discussion and resolution states. Confirm that each feedback comment either received engagement followed by an implementing commit or convinced the reviewer to retract it.

✅ Passed checks (6 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title uses the allowed refactor: prefix, starts the description with a capital letter, and clearly describes the semver dependency update.
Linked Issues check	✅ Passed	Issue #583 requires the direct semver devDependency upgrade from 7.7.4 to 7.8.5. package.json declares semver at 7.8.5. The PR summary records the matching root and top-level lock-file resolutio…
Out of Scope Changes check	✅ Passed	The reviewed changes are limited to the semver manifest update and lock-file resolution changes. The nested parse-server entry at 7.7.4 is a transitive dependency resolution and does not expand th…
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Security Check	✅ Passed	PASS. The authoritative diff changes only package.json and package-lock.json, upgrading the root semver development dependency from 7.7.4 to 7.8.5 with matching npm integrity metadata. No applic…

Full details: Engage In Review Feedback

Explanation

The current review reports zero actionable findings, but it explicitly does not establish whether earlier review comments exist or were resolved. The available evidence cannot confirm that the contributor engaged with all review feedback before implementing or retracting it.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

Warning

Some tools did not complete. Review the errors below.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

package.json

ESLint skipped: missing config or dependency (missing-dependency). The ESLint configuration references a package that is not available in the sandbox.

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.77%. Comparing base (b9245cb) to head (b6bcfdd).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #603   +/-   ##
=======================================
  Coverage   97.77%   97.77%           
=======================================
  Files           2        2           
  Lines         225      225           
=======================================
  Hits          220      220           
  Misses          5        5           

☔ View full report in Codecov by Harness.
📢 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.