-
Notifications
You must be signed in to change notification settings - Fork 19
fix(ci): update setup-deno action to v2 for Deno 2.x compatibility #293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
WalkthroughUpdated CI workflow to use Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Tip 👮 Agentic pre-merge checks are now available in preview!Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.
Please see the documentation for more information. Example: reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"
mode: "warning"
instructions: |
Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal). Please share your feedback with us on this Discord post. 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. Comment |
Deno 2.3.0 has a known bug where fs.close() requires a callback even though it should be optional according to Node.js documentation. This causes test failures with "TypeError: callback is not a function" errors. Using Deno 2.1.4 as the minimum tested version instead, while keeping 2.x for testing with the latest version. See: denoland/deno#30718
This reverts commit 59d7df9.
The CI failures are caused by msgpackr (a dependency of @denops/core v8) requiring lifecycle scripts to properly initialize its native extensions. Without these scripts, tests fail with "TypeError: callback is not a function" errors in fs.close(). Setting nodeModulesDir to "auto" allows Deno to run these lifecycle scripts and properly initialize the msgpackr native extensions.
…test The CI failures were caused by a version mismatch between @denops/core and @denops/test. The project was using @denops/core v8, but @denops/test v3.0.4 is hardcoded to use @denops/core v7. This mismatch caused the fs.close() errors in the Linux CI environment. Until @denops/test is updated to support @denops/core v8, we need to stay on v7 to maintain compatibility.
The CI failures were caused by @denops/test v3.0.4 being hardcoded to use @denops/core v7, while the project uses v8. This version mismatch caused fs.close() errors in the Linux CI environment. Updating to @denops/test v3.1.0 which supports @denops/core v8.
diff --git a/deno.jsonc b/deno.jsonc
index 476dafd..0353732 100644
--- a/deno.jsonc
+++ b/deno.jsonc
@@ -48,7 +48,7 @@
"@core/asyncutil": "jsr:@core/asyncutil@^1.2.0",
"@core/unknownutil": "jsr:@core/unknownutil@^4.3.0",
"@denops/core": "jsr:@denops/core@^8.0.0",
- "@denops/test": "jsr:@denops/test@^3.1.0",
+ "@denops/test": "jsr:@denops/test@^3.0.0",
"@lambdalisue/errorutil": "jsr:@lambdalisue/errorutil@^1.1.1",
"@lambdalisue/itertools": "jsr:@lambdalisue/itertools@^1.1.2",
"@lambdalisue/unreachable": "jsr:@lambdalisue/unreachable@^1.0.1", fixes the error. Because |
Because denops/test 3.1.0 don't exist
So
The errors are reproduced. |
🎯 Purpose
Fix CI failures caused by version incompatibility between @denops/core and @denops/test.
📝 Description
What Changed
denoland/setup-deno@v1.1.4
todenoland/setup-deno@v2
in the test job@denops/core
from v8.0.0 back to v7.0.0Root Cause
The CI started failing after upgrading @denops/core from v7 to v8. The issue is that @denops/test v3.0.4 is hardcoded to use
@denops/core@^7.0.0
, creating a version conflict when the project uses v8.This mismatch caused runtime errors that manifested as "TypeError: callback is not a function" in fs.close() when running tests in the Linux CI environment.
🔄 Type of Change
🧪 Testing
Root Cause Analysis
Expected Result
With @denops/core downgraded to v7, both the project and @denops/test will use the same version, eliminating the conflict.
✅ Checklist
Code Quality
Testing
🔗 Related Issues
Fixes CI failures that started from: c720851
📊 Impact
This temporarily downgrades @denops/core to v7 to maintain compatibility with @denops/test. When @denops/test is updated to support v8, the project can upgrade again.
📝 Next Steps
Summary by CodeRabbit