Bump versions

[lambdalisue]

Summary

• Updated @denops/core from ^7.0.0 to ^8.0.0
• Updated @denops/test from ^3.0.1 to ^3.0.4
• Updated @lambdalisue/errorutil from ^1.0.0 to ^1.1.1
• Updated multiple @std packages to latest versions
• Updated encoding-japanese from ^2.1.0 to ^2.2.0

Test plan

• Dependencies updated in deno.jsonc
• Run tests to ensure compatibility
• Verify all imports work correctly

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated multiple dependencies to newer versions for improved stability and compatibility.
  • Includes updates to core runtime libraries and testing tools.
  • No functional changes to features or public APIs.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request updates dependency version ranges in deno.jsonc imports, bumping @denops, @std modules, @lambdalisue/errorutil, @denops/test, and npm:encoding-japanese. No code, API, or export changes are included.

Changes

Cohort / File(s)	Change summary
Dependency version bumps deno.jsonc	Updated import versions: @denops/core ^7.0.0→^8.0.0, @denops/test ^3.0.1→^3.0.4, @lambdalisue/errorutil ^1.0.0→^1.1.1, @std/assert ^1.0.0→^1.0.14, @std/collections ^1.0.9→^1.1.3, @std/fs ^1.0.0→^1.0.19, @std/path ^1.0.2→^1.1.2, @std/semver ^1.0.0→^1.0.5, @std/streams ^1.0.0→^1.0.11, @std/testing ^1.0.1→^1.0.15, encoding-japanese ^2.1.0→^2.2.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• 📦 bump @std/semver from 0.224.3 to 1.0.0 #254 — Also updates the @std/semver entry in deno.jsonc, preceding this PR’s further bump within the ^1.0.x range.

Poem

I hop through json fields with care,
Nudging versions here and there.
Carrots tall, dependencies neat,
Semver steps with bunny feet.
One file tweaked, the garden’s bright—
Ship it now, the build’s just right! 🥕🐇

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 43c7856 and c720851.

📒 Files selected for processing (1)

• deno.jsonc (1 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bump-versions

---

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

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.77%. Comparing base (43c7856) to head (c720851).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #291   +/-   ##
=======================================
  Coverage   84.77%   84.77%           
=======================================
  Files          64       64           
  Lines        2864     2864           
  Branches      278      278           
=======================================
  Hits         2428     2428           
  Misses        434      434           
  Partials        2        2           

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