Bump dependencies

[hawkeyexl]

Summary by CodeRabbit

• Chores
  • Updated the overall application version to a development release format.
  • Upgraded core dependencies to incorporate the latest fixes and improvements for enhanced stability and performance.

[coderabbitai]

Walkthrough

The update modifies the package.json file by shifting the version to a development release and incrementing several dependency versions. Specifically, the version is changed from "2.19.0" to "2.19.0-dev.0" and the dependencies appium-geckodriver, appium-safari-driver, and doc-detective-common are updated to newer versions.

Changes

File(s)	Change Summary
package.json	- Version updated from "2.19.0" to "2.19.0-dev.0" - appium-geckodriver updated from "^1.4.1" to "^1.4.2" - appium-safari-driver updated from "^3.5.21" to "^3.5.22" - doc-detective-common updated from "1.22.0-dev.1" to "1.22.0-dev.2"

Possibly related PRs

• Update ajv and doc-detective-common dependencies #248: Updates the doc-detective-common dependency version, directly relating to the changes in this PR.
• Update dependencies #247: Focuses on dependency updates in package.json, aligning with the modifications in this PR.

Suggested labels

dependencies, size:S

Poem

Hoppin' through the code, I see,
A dev version shines so bright and free.
Dependencies updated, line by line,
In my burrow of code, everything’s just fine.
With each new version, my heart takes flight –
A rabbit’s song in the soft moonlight!

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bd5f98d and 15a3bd1.

⛔ 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)

⏰ Context from checks skipped due to timeout of 90000ms (9)

• GitHub Check: test (macos-latest, 22)
• GitHub Check: test (macos-latest, 20)
• GitHub Check: test (macos-latest, 18)
• GitHub Check: test (windows-latest, 22)
• GitHub Check: test (windows-latest, 20)
• GitHub Check: test (windows-latest, 18)
• GitHub Check: test (ubuntu-latest, 22)
• GitHub Check: test (ubuntu-latest, 20)
• GitHub Check: test (ubuntu-latest, 18)

🔇 Additional comments (4)

package.json (4)

3-3: Development Version Update in "version" Field.
The version update to "2.19.0-dev.0" clearly signals a shift to a development release. Ensure that your CI/CD process and any release management scripts handle pre-release or development identifiers as expected.

---

36-36: Dependency Bump for "appium-geckodriver".
The dependency version has been updated from "^1.4.1" to "^1.4.2". Please confirm from the release notes that there are no breaking changes and that the new version works seamlessly with your integration tests if available.

---

37-37: Dependency Bump for "appium-safari-driver".
The dependency update from "^3.5.21" to "^3.5.22" is a minor version bump. Verify that this new version is compatible with your overall setup and that any changes in behavior are documented in the release notes.

---

39-39: Dependency Bump for "doc-detective-common".
The update from "1.22.0-dev.1" to "1.22.0-dev.2" reflects a development version increment likely including bug fixes or enhancements. Ensure that downstream modules using this dependency have been tested against the updated version.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.