Update @emnapi/core 1.10.0 → 1.11.1 (minor)#20238
Conversation
Confidence Score: 5/5Routine automated dependency bump with no logic changes; all lockfile entries are consistent with the new version. Only two files changed: a package.json version specifier and its generated lockfile. The new @emnapi/core 1.11.1 is a minor release that adds WASI-level N-API helpers and fixes a shared-memory-buffer atomics bug — nothing that touches Tailwind's own code. All lockfile snapshot entries that reference the old 1.10.0 peer have been updated to 1.11.1, and no entries appear inconsistent or duplicated. No files require special attention. Reviews (1): Last reviewed commit: "Update @emnapi/core to version 1.11.1" | Re-trigger Greptile |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
WalkthroughThe 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
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.10.0 → 1.11.1) · Repo
Release Notes
1.11.1
1.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.1fix: refresh stale shared memory buffer before atomic access (v1.x backport) (#218)1.11.0refactor: remove use of PThread.runningWorkers (#216)ci: workflow_dispatchfeat: support SharedArrayBuffer in napi_create_typedarray (#212)feat: add napi_create_external_sharedarraybuffer (#211)test: sync tsfn abort testDepfu 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