Update @emnapi/runtime 1.7.1 → 1.8.1 (minor)

[depfu]

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?

✳️ @​emnapi/runtime (1.7.1 → 1.8.1) · Repo

Release Notes

1.8.1

What's Changed

• feat: add support for Float16Array by @toyobayashi in #190

Full Changelog: v1.8.0...v1.8.1

1.8.0

What's Changed

• feat: add node_api_set_prototype by @toyobayashi in #188

Full Changelog: v1.7.1...v1.8.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 4 commits:

• 1.8.1
• [Backport] feat: add support for Float16Array (#191)
• 1.8.0
• [Backport] feat: add node_api_set_prototype (#189)

---

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

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[coderabbitai]

Walkthrough

The change updates the @emnapi/runtime dependency version in the package.json file for the wasm32-wasi npm package. The version constraint was updated from ^1.7.1 to ^1.8.1. This represents a minor version bump that allows for compatible updates within the 1.8.x release range. No other dependencies were modified, and no public API exports or declarations were changed.

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: updating @emnapi/runtime from version 1.7.1 to 1.8.1, which matches the changeset perfectly.
Description check	✅ Passed	The description provides detailed information about the dependency update, including release notes, changelog details, and commit information, all directly related to the changeset.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @crates/node/npm/wasm32-wasi/package.json:
- Around line 31-32: The package.json dependency versions for @emnapi are
mismatched: "@emnapi/runtime" is "^1.8.1" while "@emnapi/core" is "^1.7.1";
update the version string for "@emnapi/core" to "^1.8.1" to match
"@emnapi/runtime" (or if you prefer to lock to 1.7.1, change "@emnapi/runtime"
to "^1.7.1"), ensuring both @emnapi/core and @emnapi/runtime use identical
versions.

📜 Review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7971167 and e4fff4e.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• crates/node/npm/wasm32-wasi/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: Linux / upgrade
• GitHub Check: Linux / postcss
• GitHub Check: Linux / cli
• GitHub Check: Linux / vite
• GitHub Check: Windows
• GitHub Check: Linux
• GitHub Check: macOS

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

@emnapi/core npm package latest version

💡 Result:

The latest published version appears to be 1.7.1. [1][2]

Sources:

• Socket.dev package listing (shows 1.7.1). [1]
• npm package page (official npm listing shows older versions; double-check npm registry if you need definitive registry data). [2]

---

🌐 Web query:

@emnapi/runtime 1.8.1 @emnapi/core compatibility

💡 Result:

Short answer: Use matching versions — @emnapi/runtime 1.8.1 should be used with @emnapi/core 1.8.1. The emnapi README states “Each package should match the same version,” and the docs show @emnapi/runtime and @emnapi/core used together. [1][2]

Sources:

• emnapi GitHub README — “Each package should match the same version.” [1]
• emnapi docs / Getting Started (shows runtime + core used together). [2]

---

🌐 Web query:

@emnapi/core security vulnerabilities CVE

💡 Result:

I found no CVE entries for @emnapi/core and no direct vulnerabilities reported in major vulnerability trackers (npm package page and Snyk). [1][2]

Sources:
[1] npm package page for @emnapi/core. [2] Snyk vulnerability listing for @emnapi/core.

---

Update @emnapi/core to match @emnapi/runtime version.

The emnapi documentation explicitly requires that all @emnapi packages use matching versions. Currently, @emnapi/runtime is at 1.8.1 while @emnapi/core remains at 1.7.1. Update @emnapi/core to 1.8.1 to maintain version alignment, or downgrade @emnapi/runtime to 1.7.1 if 1.8.1 is not yet available for @emnapi/core.

🤖 Prompt for AI Agents

In @crates/node/npm/wasm32-wasi/package.json around lines 31 - 32, The
package.json dependency versions for @emnapi are mismatched: "@emnapi/runtime"
is "^1.8.1" while "@emnapi/core" is "^1.7.1"; update the version string for
"@emnapi/core" to "^1.8.1" to match "@emnapi/runtime" (or if you prefer to lock
to 1.7.1, change "@emnapi/runtime" to "^1.7.1"), ensuring both @emnapi/core and
@emnapi/runtime use identical versions.

[depfu]

Sorry, but the merge failed with:

At least 1 approving review is required by reviewers with write access.