Skip to content

chore(deps): update dependency oxlint to v1.7.0 #775

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update dependency oxlint to v1.7.0 #775

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 12, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
oxlint (source) 1.5.0 -> 1.7.0 age confidence

Release Notes

oxc-project/oxc (oxlint)

v1.7.0

Compare Source

🚀 Features
  • a4dae73 linter: Introduce LintPlugins to store builtin + custom plugins (#​12117) (camc314)

v1.6.0: oxlint v1.6.0

Compare Source

[1.6.0] - 2025-07-07

🐛 Bug Fixes
  • 3f0e03e linter: Fix inconsistent behavior in no-duplicate-imports rule (#​12051) (yefan)
  • 6dbacea linter/no-barrel-file: No diagnostic tag when some modules arent resolved (#​12049) (camc314)
  • dd6b1ee linter/extensions: False positives with non configured extensions (#​11872) (camc314)
  • 5851d2c oxlint: Always follow symlinks; remove cli flag --symlinks (#​12048) (Boshen)
  • eb1c596 linter/consistent-index-object-style: Fix default impl for rule config (#​12031) (camc314)
🚜 Refactor
📚 Documentation
  • 85ec382 linter: Add good/bad example for nextjs/no-page-custom-font (#​12092) (Sysix)
  • 9240342 linter: Add docs for nextjs/no-script-component-in-head (#​12091) (Sysix)
  • 0878414 linter: Add good/bad example for nextjs/no-head-import-in-document (#​12061) (Sysix)
  • 222bc73 linter: Add bad/good example for nextjs/no-head-element (#​12059) (Sysix)
  • a7e9f50 linter: Add good/bad example for nextjs/no-title-in-document-head (#​12065) (Sysix)
  • 51c6818 linter: Add good/bad example for nextjs/no-document-import-in-pages (#​12064) (Sysix)
  • c7b38f9 consistent-indexed-object-style: Clarify docs (#​12019) (Luca Ban)
⚡ Performance
  • 04e2de5 linter: Avoid iteration when checking import is AllButDefault or SideEffect in eslint/no-duplicate-imports (#​12093) (Sysix)
  • e2a7d6a linter: Check filepath before running nextjs/no-head-element (#​12062) (Sysix)
  • 00a9fd9 linter: Check for filename before running nextjs/no-head-import-in-document rule (#​12060) (Sysix)
  • 62a3ce0 linter: Replace unicode-segmentation crate with icu_segmenter (#​12063) (Sysix)

Configuration

📅 Schedule: Branch creation - "every weekend" (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.

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

@coderabbitai coderabbitai
Copy link

coderabbitai bot commented Jul 12, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@renovate renovate bot force-pushed the renovate/oxlint-monorepo branch from e7f46a3 to 90d4394 Compare July 17, 2025 00:24
@renovate renovate bot changed the title chore(deps): update dependency oxlint to v1.6.0 chore(deps): update dependency oxlint to v1.7.0 Jul 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants