☕ (ci) bump denoland/setup-deno from v1 to v2

[Milly]

Summary by CodeRabbit

• Chores
  • Updated workflow to use a consistent matrix key for Deno versions.
  • Upgraded the Deno setup action in the workflow to a newer version.

[coderabbitai]

Walkthrough

The workflow configuration was updated to rename the Deno version matrix key from version to deno_version and to reference this new key throughout. Additionally, the Deno setup GitHub Action was upgraded from version 1 to version 2 in both the check and test jobs.

Changes

File(s)	Change Summary
.github/workflows/test.yml	Renamed matrix key from version to deno_version; updated all references; upgraded Deno setup action from v1 to v2.

Possibly related PRs

• vim-denops/denops.vim#395: Updates the Deno setup action within the v1 major version in a different workflow file, sharing a focus on Deno setup action changes.

Suggested reviewers

• lambdalisue

Poem

In the warren where workflows run,
A rabbit tweaks the matrix for fun.
Deno’s version gets a shiny new name,
And setup jumps to v2 in the game.
With carrots and code, we hop ahead,
Leaving old versions snug in their bed! 🥕

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

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

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @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.

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

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.99%. Comparing base (8ee1fcc) to head (0627241).
Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #449   +/-   ##
=======================================
  Coverage   96.99%   96.99%           
=======================================
  Files          27       27           
  Lines        1462     1462           
  Branches      189      190    +1     
=======================================
  Hits         1418     1418           
  Misses         40       40           
  Partials        4        4           

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

[coderabbitai]

Actionable comments posted: 0

♻️ Duplicate comments (1)

.github/workflows/test.yml (1)

85-88: Same pin-version & input-name observations as in the check job

Mirror whatever decision you take for the check job (v2.x.y pinning, input validation).

🧹 Nitpick comments (2)

.github/workflows/test.yml (2)

43-46: Action bumped to setup-deno@v2 – pin minor/patch to avoid surprise breaks

v2 will float to every new minor/patch release. To keep CI reproducible you may prefer an explicit tag such as v2.1.0 (or whatever is current).

-      - uses: denoland/setup-deno@v2
+      - uses: denoland/[email protected]

Also verify the input name remains deno-version in v2 (docs say yes, but safer to confirm).

---

69-72: Matrix expansion LGTM – consider limiting to a single “latest 1.x” if runtime minutes explode

Testing explicit 1.45.0, 1.x, and 2.x gives great coverage, but triples job count.
If CI time becomes an issue, pick one fixed 1.x or rely on 1.x rolling forward.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8ee1fcc and 0627241.

📒 Files selected for processing (1)

• .github/workflows/test.yml (2 hunks)

🧰 Additional context used

🧠 Learnings (1)

.github/workflows/test.yml (1)

Learnt from: Milly
PR: vim-denops/denops.vim#418
File: tests/denops/runtime/functions/plugin/check_type_test.ts:6-6
Timestamp: 2024-09-14T17:09:30.174Z
Learning: In this project, import paths prefixed with `/denops-testdata/` are defined in `deno.jsonc` via an import map, and these import paths are valid.

🔇 Additional comments (1)

.github/workflows/test.yml (1)

35-38: No lingering ${{ matrix.version }} references found

Confirmed with a repository-wide search that all references have been updated to matrix.deno_version.