Update @emnapi/runtime 1.10.0 → 1.11.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.10.0 → 1.11.1) · Repo

Release Notes

1.11.1

What's Changed

• fix: refresh stale shared memory buffer before atomic access (v1.x backport) by @Brooooooklyn in #218

New Contributors

• @Brooooooklyn made their first contribution in #218

Full Changelog: v1.11.0...v1.11.1

1.11.0

What's Changed

• feat: add napi_create_external_sharedarraybuffer (#211)
• feat: support SharedArrayBuffer in napi_create_typedarray (#212)
• refactor: remove use of PThread.runningWorkers (#216)

Full Changelog: v1.10.0...v1.11.0

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

Commits

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

• 1.11.1
• fix: refresh stale shared memory buffer before atomic access (v1.x backport) (#218)
• 1.11.0
• refactor: remove use of PThread.runningWorkers (#216)
• ci: workflow_dispatch
• feat: support SharedArrayBuffer in napi_create_typedarray (#212)
• feat: add napi_create_external_sharedarraybuffer (#211)
• test: sync tsfn abort test

---

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)

[greptile-apps]

Confidence Score: 5/5

Straightforward lockfile-only dependency bump with no application logic changes; the lockfile is internally consistent.

The change touches only package.json and pnpm-lock.yaml. All peer-dependency snapshot variants are updated in tandem and the old 1.10.0 snapshot is correctly retained as optional for any remaining dependents. The upstream changelog contains only a targeted bug fix and additive features with no breaking changes.

No files require special attention.

_{Reviews (1): Last reviewed commit: "Update @emnapi/runtime to version 1.11.1" | Re-trigger Greptile}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 9a7ef229-f29a-4e9f-bdce-4b102609f705

📥 Commits

Reviewing files that changed from the base of the PR and between 8a14a71 and 0b01dc3.

⛔ 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

---

Walkthrough

The @emnapi/runtime dependency in crates/node/npm/wasm32-wasi/package.json is updated from ^1.10.0 to ^1.11.1. No other fields or dependencies in the file are changed.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and clearly describes the main change: updating @emnapi/runtime dependency from version 1.10.0 to 1.11.1.
Description check	✅ Passed	The description is directly related to the changeset, providing detailed release notes and commit history for the @emnapi/runtime update.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ 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.}