chore(deps): update napi

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@napi-rs/cli (source)	3.7.0 → 3.7.1					pnpm.catalog.default	patch
napi	3.9.0 → 3.9.1					workspace.dependencies	patch

---

Release Notes

napi-rs/napi-rs (@​napi-rs/cli)

v3.7.1

Compare Source

What's Changed

• fix: receive error message from worker correctly by @​sapphi-red in #​3300
• chore(deps): update dependency npm-run-all2 to v9 by @​renovate[bot] in #​3299
• fix(cli): NAPI_RS_FORCE_WASI only activates on 'true' or 'error' by @​MukundaKatta in #​3236

New Contributors

• @​MukundaKatta made their first contribution in #​3236

Full Changelog: https://github.com/napi-rs/napi-rs/compare/napi-v3.9.0...@​napi-rs/cli@3.7.1

---

Configuration

📅 Schedule: (in timezone Asia/Shanghai)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​napi@​3.9.0 ⏵ 3.9.1
	npm/​@​napi-rs/​cli@​3.7.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm js-yaml is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@napi-rs/cli@3.7.1 → npm/js-yaml@4.2.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-yaml@4.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report