chore(deps): update dependency oxfmt to ^0.51.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
oxfmt (source)	^0.45.0 → ^0.51.0

---

Release Notes

oxc-project/oxc (oxfmt)

v0.51.0

Compare Source

v0.50.0

Compare Source

🐛 Bug Fixes

• 43b9978 formatter/sort_imports: Treat subpath imports as internal (#​22440) (leaysgur)

v0.49.0

Compare Source

🚀 Features

• 6e8e818 oxfmt: Experimental .svelte support (#​21700) (leaysgur)

v0.48.0

Compare Source

v0.47.0

Compare Source

v0.46.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

? Verifying lockfile against supply-chain policies (381 entries)...
✗ Lockfile failed supply-chain policy check (381 entries in 2s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 20 lockfile entries failed verification:
  @oxlint/binding-android-arm-eabi@1.66.0 was published at 2026-05-19T08:07:03.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-android-arm64@1.66.0 was published at 2026-05-19T08:06:33.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-darwin-arm64@1.66.0 was published at 2026-05-19T08:06:27.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-darwin-x64@1.66.0 was published at 2026-05-19T08:07:50.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-freebsd-x64@1.66.0 was published at 2026-05-19T08:08:01.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-linux-arm-gnueabihf@1.66.0 was published at 2026-05-19T08:07:08.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-linux-arm-musleabihf@1.66.0 was published at 2026-05-19T08:07:13.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-linux-arm64-gnu@1.66.0 was published at 2026-05-19T08:06:46.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-linux-arm64-musl@1.66.0 was published at 2026-05-19T08:06:52.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-linux-ppc64-gnu@1.66.0 was published at 2026-05-19T08:07:25.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-linux-riscv64-gnu@1.66.0 was published at 2026-05-19T08:07:31.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-linux-riscv64-musl@1.66.0 was published at 2026-05-19T08:07:36.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-linux-s390x-gnu@1.66.0 was published at 2026-05-19T08:07:44.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-linux-x64-gnu@1.66.0 was published at 2026-05-19T08:08:08.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-linux-x64-musl@1.66.0 was published at 2026-05-19T08:08:14.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-openharmony-arm64@1.66.0 was published at 2026-05-19T08:06:58.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-win32-arm64-msvc@1.66.0 was published at 2026-05-19T08:06:40.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-win32-ia32-msvc@1.66.0 was published at 2026-05-19T08:07:19.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  @oxlint/binding-win32-x64-msvc@1.66.0 was published at 2026-05-19T08:07:55.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)
  oxlint@1.66.0 was published at 2026-05-19T08:08:21.000Z, within the minimumReleaseAge cutoff (2026-05-19T07:47:34.468Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.