chore: release v11.8.1

[Boshen]

🤖 New release

• oxc_resolver: 11.8.0 -> 11.8.1
• oxc_resolver_napi: 11.8.0 -> 11.8.1

Changelog

oxc_resolver

11.8.1 - 2025-09-16

💼 Other

• Revert "perf: use memmap to speed up file reading" (#701) (by @Boshen) - Revert "perf: use memmap to speed up file reading" #701

Contributors

• @Boshen

---

This PR was generated with release-plz.

[graphite-app]

How to use the Graphite Merge Queue

Add the label merge to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.89%. Comparing base (9eeb3bb) to head (f8655b7).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #702   +/-   ##
=======================================
  Coverage   94.89%   94.89%           
=======================================
  Files          12       12           
  Lines        2882     2882           
=======================================
  Hits         2735     2735           
  Misses        147      147           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[codspeed-hq]

CodSpeed Performance Report

Merging #702 will not alter performance

_{Comparing release-plz-2025-09-16T02-53-38Z (f8655b7) with main (ae725f4)¹}

Summary

✅ 7 untouched
⏩ 2 skipped²

Footnotes

1. No successful run was found on main (9eeb3bb) during the generation of this report, so ae725f4 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩