Update oxlint monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
oxfmt (source)	^0.26.0 → ^0.33.0
oxlint (source)	1.41.0 → 1.48.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

oxc-project/oxc (oxfmt)

v0.33.0

Compare Source

💥 BREAKING CHANGES

• 9c34f72 formatter/sort_imports: [BREAKING] Report invalid group name with renaming side-effect > side_effect (#​19416) (leaysgur)

🚀 Features

• 4baebef formatter/sort_imports: Support { newlinesBetween: bool } inside groups (#​19358) (leaysgur)
• d1c2fb6 formatter/sort_imports: Support customGroups attributes(selector and modifiers) (#​19356) (leaysgur)

v0.32.0

Compare Source

v0.30.0

🐛 Bug Fixes

• 1b2f354 ci: Add missing riscv64/s390x napi targets for oxfmt and oxlint (#​19217) (Cameron)

v0.28.0

Compare Source

v0.27.0

Compare Source

📚 Documentation

• 8ccd853 npm: Update package homepage URLs and add keywords (#​18509) (Boshen)

oxc-project/oxc (oxlint)

v1.48.0

Compare Source

v1.47.0

Compare Source

v1.45.0

🐛 Bug Fixes

• 1b2f354 ci: Add missing riscv64/s390x napi targets for oxfmt and oxlint (#​19217) (Cameron)

v1.43.0

Compare Source

v1.42.0

Compare Source

🚀 Features

• 15d69dc linter: Implement react/display-name rule (#​18426) (camchenry)

📚 Documentation

• 8ccd853 npm: Update package homepage URLs and add keywords (#​18509) (Boshen)

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone UTC, 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.

👻 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.

[greptile-apps]

Greptile Overview

Greptile Summary

• Updates the pnpm catalog/lock resolution for oxfmt to 0.27.0 and oxlint to 1.42.0.
• pnpm-workspace.yaml only bumps oxfmt, leaving oxlint pinned to ^1.41.0.
• pnpm-lock.yaml simultaneously resolves oxlint to 1.42.0 but drops the catalogs.default.oxlint entry, creating catalog/lock inconsistency and likely lockfile churn on the next install.

Confidence Score: 2/5

• Not safe to merge as-is due to catalog/lock inconsistencies that will churn or break installs.
• The PR intends to bump oxlint, but the workspace catalog remains on ^1.41.0 while the lock resolves 1.42.0 and also removes the lockfile catalog entry for oxlint. This inconsistency will not be stable under pnpm catalog resolution and should be fixed before merging.
• pnpm-workspace.yaml and pnpm-lock.yaml

Important Files Changed

Filename	Overview
pnpm-lock.yaml	Updates oxfmt to 0.27.0 and oxlint to 1.42.0 in lockfile, but the lockfile also removes the catalog entry for oxlint, creating an inconsistency with workspace catalog usage.
pnpm-workspace.yaml	Bumps oxfmt catalog to ^0.27.0 but leaves oxlint at ^1.41.0, which conflicts with pnpm-lock.yaml resolving oxlint to 1.42.0 via catalog specifier.

[greptile-apps]

_{2 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (2)

pnpm-workspace.yaml
Catalog/lock mismatch
pnpm-lock.yaml now resolves oxlint to 1.42.0 (via specifier: 'catalog:'), but pnpm-workspace.yaml still pins oxlint: ^1.41.0. With pnpm catalogs, the lockfile should reflect the workspace catalog versions; this inconsistency will flip back on the next pnpm install/Renovate run. Update the workspace catalog entry to oxlint: ^1.42.0 to match the intended bump.

Prompt To Fix With AI

This is a comment left during a code review.
Path: pnpm-workspace.yaml
Line: 14:22

Comment:
**Catalog/lock mismatch**
`pnpm-lock.yaml` now resolves `oxlint` to `1.42.0` (via `specifier: 'catalog:'`), but `pnpm-workspace.yaml` still pins `oxlint: ^1.41.0`. With pnpm catalogs, the lockfile should reflect the workspace catalog versions; this inconsistency will flip back on the next `pnpm install`/Renovate run. Update the workspace catalog entry to `oxlint: ^1.42.0` to match the intended bump.

How can I resolve this? If you propose a fix, please make it concise.

---

pnpm-lock.yaml
Lockfile catalog entry removed
In catalogs.default, the oxlint entry was removed even though importers still use oxlint with specifier: 'catalog:' and the workspace still defines an oxlint catalog version. This will cause pnpm-lock.yaml to churn (and can break reproducibility of catalog resolution). Re-add the oxlint catalog entry (specifier/version) so the lockfile’s catalog section matches the workspace catalog usage.

Prompt To Fix With AI

This is a comment left during a code review.
Path: pnpm-lock.yaml
Line: 37:46

Comment:
**Lockfile catalog entry removed**
In `catalogs.default`, the `oxlint` entry was removed even though importers still use `oxlint` with `specifier: 'catalog:'` and the workspace still defines an `oxlint` catalog version. This will cause `pnpm-lock.yaml` to churn (and can break reproducibility of catalog resolution). Re-add the `oxlint` catalog entry (specifier/version) so the lockfile’s catalog section matches the workspace catalog usage.

How can I resolve this? If you propose a fix, please make it concise.