Update dependencies to latest versions

[hawkeyexl]

Update the project dependencies to their latest versions, including updates to doc-detective-common, posthog-node, and several others, ensuring compatibility and improved functionality.

Summary by CodeRabbit

• Chores
  • Updated project dependencies to the latest compatible versions to maintain compatibility and security.
  • Development version bumped to 3.5.1-dev.0 for ongoing development.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Package version incremented to 3.5.1-dev.0 with corresponding updates to the doc-detective-common dependency. Minor version bumps applied to posthog-node and body-parser dev dependency.

Changes

Cohort / File(s)	Summary
Package version and dependency updates package.json	Version bumped from 3.5.0 to 3.5.1-dev.0; doc-detective-common updated to ^3.5.1-dev.0; posthog-node upgraded to ^5.14.0; body-parser dev dependency updated to ^2.2.1

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• All changes are straightforward dependency version updates with no code logic alterations
• Single file affected with homogeneous, repetitive nature of changes
• No API or behavior modifications introduced

Poem

🐰 Deps hop up, versions dance,
3.5.1-dev takes its chance,
PostHog leaps, body-parser springs,
A rabbit's joy when update rings! 🎉

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update dependencies to latest versions' is a vague, generic description that doesn't specify which dependencies were updated or their significance. It lacks specificity about the actual changes made.	Consider using a more specific title that highlights key updates, such as 'Update doc-detective-common and posthog-node to latest versions' or 'Bump package version to 3.5.1-dev.0 and update dependencies'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch enhanced-find-goto-draganddrop

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cb2018b and 1a15f64.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (2 hunks)

🔇 Additional comments (4)

package.json (4)

3-3: Verify pre-release version is intentional for main branch.

The package version is being bumped to a pre-release version (3.5.1-dev.0). Pre-release versions are typically reserved for development and testing, not for release to the main branch. Confirm this is intentional.

---

36-36: Patch version bump is low-risk.

The update to body-parser@^2.2.1 is a patch version bump. Since this is a devDependency, the update introduces minimal risk.

---

33-33: posthog-node@5.14.0 is the safe, recommended version following a supply chain incident.

The upgrade from ^5.13.0 to ^5.14.0 is verified as secure. PostHog unpublished compromised versions (4.18.1, 5.11.3, 5.13.3) following a November 24, 2025 npm supply chain compromise and recommends upgrading to 5.14.0. Snyk confirms no known security issues in this version. The change is appropriate and actually improves security posture by moving to the official safe release.

---

30-30: Pre-release dependency is intentional and properly published; concern about availability is unfounded.

The version doc-detective-common@3.5.1-dev.0 is published on npm with proper integrity and is available for installation. This is a coordinated development version across the monorepo (the resolver project itself is also at 3.5.1-dev.0), tagged as enhancedFind on npm. While using pre-release versions in production should be avoided, this appears to be appropriate for a feature/development branch. If this is intended for production release, ensure the dependency is updated to the stable 3.5.0 before merging.

---

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

[Copilot]

Pull request overview

This PR attempts to update project dependencies to their latest versions, including bumping the development version to 3.5.1-dev.0. However, multiple critical issues have been identified with non-existent package versions.

• Version bump from 3.5.0 to 3.5.1-dev.0 for ongoing development
• Updates to doc-detective-common, posthog-node, and body-parser
• Several transitive dependency updates through body-parser

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
package.json	Updated project version to 3.5.1-dev.0 and attempted to update dependencies including doc-detective-common, posthog-node, and body-parser to non-existent versions
package-lock.json	Lock file updates reflecting the dependency changes, but contains multiple references to package versions that do not exist in npm registry

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.