-
-
Notifications
You must be signed in to change notification settings - Fork 5k
Update @emnapi/core 1.7.1 → 1.8.1 (minor) #19546
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
WalkthroughThe 🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @crates/node/npm/wasm32-wasi/package.json:
- Line 31: Update the dependency version for @emnapi/runtime to match
@emnapi/core by changing the @emnapi/runtime entry from ^1.7.1 to ^1.8.1 in
package.json so both @emnapi/core and @emnapi/runtime use ^1.8.1; ensure
package.json has "@emnapi/runtime": "^1.8.1" and run your package manager
install to update lockfiles.
📜 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/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: macOS
- GitHub Check: Windows
- GitHub Check: Linux
- GitHub Check: Linux / upgrade
- GitHub Check: Linux / vite
- GitHub Check: Linux / postcss
- GitHub Check: Linux / cli
| "dependencies": { | ||
| "@napi-rs/wasm-runtime": "^1.1.1", | ||
| "@emnapi/core": "^1.7.1", | ||
| "@emnapi/core": "^1.8.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
cat crates/node/npm/wasm32-wasi/package.jsonRepository: tailwindlabs/tailwindcss
Length of output: 1109
🏁 Script executed:
# Check if @emnapi/core version 1.8.1 exists and get version info
npm view @emnapi/core@1.8.1 version 2>&1 || echo "Version not found or npm unavailable"
npm view @emnapi/core versions --json 2>&1 | tail -20Repository: tailwindlabs/tailwindcss
Length of output: 284
🌐 Web query:
@emnapi/core 1.8.1 npm package release changelog features
💡 Result:
I couldn't find an official changelog or release notes specifically listing the features for @emnapi/core v1.8.1. NPM/Snyk show v1.8.1 as the latest published version, but the repository's GitHub release/tags or a CHANGELOG.md referencing 1.8.1 wasn't found in my search. Sources checked:
- @emnapi/core package pages on npm. [1][2]
- Snyk package page showing latest version 1.8.1. [3]
- emnapi GitHub repository (no release notes/CHANGELOG entry for 1.8.1 found). [4]
If you want, I can:
- Check the repo tags/releases again and open the v1.8.1 tag if present, or
- Inspect the package tarball from the npm registry to extract the publish commit / package.json / changelog contents.
Which would you prefer?
🌐 Web query:
@emnapi/runtime @emnapi/core compatibility version requirements
💡 Result:
Short answer: @emnapi/runtime and @emnapi/core must use the same package version — install matching versions (exactly the same release). [1][2]
Sources:
- emnapi Getting Started (tips: "Each package should match the same version"). [1]
- emnapi npm page (same recommendation). [2]
Update @emnapi/runtime to ^1.8.1 to match @emnapi/core.
The @emnapi packages require matching versions. Both @emnapi/core (line 31) and @emnapi/runtime (line 32) must be at the same version. Update @emnapi/runtime from ^1.7.1 to ^1.8.1.
🤖 Prompt for AI Agents
In @crates/node/npm/wasm32-wasi/package.json at line 31, Update the dependency
version for @emnapi/runtime to match @emnapi/core by changing the
@emnapi/runtime entry from ^1.7.1 to ^1.8.1 in package.json so both @emnapi/core
and @emnapi/runtime use ^1.8.1; ensure package.json has "@emnapi/runtime":
"^1.8.1" and run your package manager install to update lockfiles.
|
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?
✳️ @emnapi/core (1.7.1 → 1.8.1) · Repo
Release Notes
1.8.1
1.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