Skip to content

chore(deps): update dependency oxlint to ~1.82.0 - #86

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/oxlint-monorepo
Oct 7, 2026
Merged

renovate[bot] merged 1 commit into
mainfrom
renovate/oxlint-monorepo

Conversation

@renovate

@renovate renovate Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
oxlint (source) ~1.81.0 → ~1.82.0 age confidence

Release Notes

oxc-project/oxc (oxlint)

v1.82.0

Compare Source

🚀 Features
  • 6a0e19c linter/eslint/no-unmodified-loop-condition: Support checkConditionalExpressions option (#​26249) (camc314)

Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • "after 10am and before 4pm every weekday"

🚦 Automerge: Enabled.

♻ 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
renovate Bot requested a review from nsheaps as a code owner October 7, 2026 19:46
@renovate
renovate Bot enabled auto-merge (squash) October 7, 2026 19:46
@renovate
renovate Bot merged commit 5aa95ad into main Oct 7, 2026
2 checks passed
@renovate
renovate Bot deleted the renovate/oxlint-monorepo branch October 7, 2026 19:46

@henry-nsheaps henry-nsheaps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

### ✅ Approve — mechanical oxlint 1.81.0 → 1.82.0 dev-dependency bump

  • ✅ Patch bump, additive upstream change, no breaking changes
  • ✅ No config conflicts with .oxlintrc.js
  • ✅ Lockfile churn is purely mechanical (1.81.0 → 1.82.0 across all @oxlint/binding-* platform packages)
  • ✅ No source code touched; devDependency only (no runtime/security surface)

Click to expand for full details

Scope

Two files changed, +83/-83 lines:

  • package.json: "oxlint": "~1.81.0" → "oxlint": "~1.82.0" (single line)
  • yarn.lock: mechanical version-string replacement for oxlint@npm:1.82.0 and every @oxlint/binding-* platform package (android, darwin, freebsd, linux variants, win32)

Upstream changelog assessment

Per the Renovate-captured oxc-project/oxc oxlint CHANGELOG for 1.82.0:

  • 🚀 Feature: linter/eslint/no-unmodified-loop-condition gains a checkConditionalExpressions option (oxc-project/oxc#26249)

That option is opt-in on an existing rule — no new default enforcement, no deprecations, no removed rules. The repo's .oxlintrc.js enables only recommended: true and typescript: true, so the delta is a no-op at the repository config layer.

Semver / range

~1.82.0 is >=1.82.0 <1.83.0 — same minor-pinned patch range convention the repo already uses for oxlint and nx. Consistent with existing style.

Previous reviews / threads

No prior reviews or comments on this PR. Nothing to minimize or resolve.

CI

Not used as basis for this review (per instructions, review the code itself). For context: build passed on both runs; version-preview failed — unrelated to this diff.

How these scores were derived

  • Quality 95 — mechanical, consistent lockfile update; nothing to critique.
  • Security N/A — devDependency only; oxlint is a lint-time tool, no runtime inclusion in distributed userscripts.
  • Simplicity 100 — single-line effective change in package.json; lockfile is auto-generated.
  • Confidence 90 — straightforward dep bump; small residual uncertainty only because I could not execute yarn install && yarn lint locally to confirm the binding set installs cleanly, but the diff is purely version-string replacement across already-published platform binaries.

Follow-ups:

None.

References

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants