Update @napi-rs/cli 3.4.1 → 3.5.1 (minor)#19528
Conversation
WalkthroughThis pull request updates the Pre-merge checks✅ Passed checks (2 passed)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI Agents
In @crates/node/package.json:
- Line 36: The package.json dependency entry for "@napi-rs/cli" currently
specifies a non-existent version "^3.5.1"; update the dependency to a valid
published version by replacing the version string for "@napi-rs/cli" in
package.json with "^3.5.0" so npm install can resolve the package. Ensure you
update only the version token for the "@napi-rs/cli" entry and run npm install
to verify resolution.
📜 Review details
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (1)
crates/node/package.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
- GitHub Check: macOS
- GitHub Check: Windows
- GitHub Check: Linux
- GitHub Check: Linux / vite
- GitHub Check: Linux / postcss
- GitHub Check: Linux / upgrade
- GitHub Check: Linux / cli
| "license": "MIT", | ||
| "devDependencies": { | ||
| "@napi-rs/cli": "^3.4.1", | ||
| "@napi-rs/cli": "^3.5.1", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@napi-rs/cli 3.5.1 release notes changelog
💡 Result:
I couldn't find any release notes or changelog entry for @napi-rs/cli version 3.5.1. The official changelog lists 3.5.0 (12/02/2025) and earlier releases — see the napi.rs changelog and the @napi-rs/cli docs. [1][2]
If you want, I can:
- watch for a 3.5.1 entry and notify you, or
- fetch the full changelog/compare URL to inspect recent commits between 3.5.0 and the repo HEAD.
Sources:
[1] napi.rs changelog (@napi-rs/cli entries).
[2] @napi-rs/cli docs / npm info.
🌐 Web query:
@napi-rs/cli npm package version 3.5.1
💡 Result:
I couldn't find a published @napi-rs/cli version 3.5.1.
- Official npm listing shows latest published version 3.1.5. [1]
- The napi.rs changelog and CDN list show a 3.5.0 release (but no 3.5.1). [2][3]
Sources: [1] npm package page, [2] napi.rs changelog, [3] jsDelivr package page.
🌐 Web query:
@napi-rs/cli breaking changes 3.4.1 to 3.5.1
💡 Result:
I couldn't find a @napi-rs/cli 3.5.1 release. The changelog shows 3.4.1 (Oct 24, 2025) and 3.5.0 (Dec 2, 2025) — 3.5.0 lists non-breaking changes (perf, dependency updates, use jsPackageName). No breaking changes are documented between 3.4.1 and 3.5.0, and there is no 3.5.1 entry in the project changelog or releases as of Jan 6, 2026. [1][2]
Sources:
- @napi-rs/cli changelog (shows 3.4.1 and 3.5.0). [1]
- NAPI-RS changelog overview. [2]
Version @napi-rs/cli@3.5.1 does not exist.
This version is not published in npm. The current stable releases are 3.4.1 (Oct 24, 2025) and 3.5.0 (Dec 2, 2025). Update the dependency to use "@napi-rs/cli": "^3.5.0" instead. The caret range ^3.5.1 will fail to resolve during npm install.
🤖 Prompt for AI Agents
In @crates/node/package.json at line 36, The package.json dependency entry for
"@napi-rs/cli" currently specifies a non-existent version "^3.5.1"; update the
dependency to a valid published version by replacing the version string for
"@napi-rs/cli" in package.json with "^3.5.0" so npm install can resolve the
package. Ensure you update only the version token for the "@napi-rs/cli" entry
and run npm install to verify resolution.
There was a problem hiding this comment.
It does exist, that's why it got updated.
There was a problem hiding this comment.
Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!
|
Sorry, but the merge failed with:
|
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @napi-rs/cli (3.4.1 → 3.5.1) · Repo
Sorry, we couldn't find anything useful about this release.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands