Skip to content
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.

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

chore(deps): update dependency eslint to v9.17.0 #52

Merged
merged 1 commit into from
Dec 16, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 16, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint (source) 9.16.0 -> 9.17.0 age adoption passing confidence

Release Notes

eslint/eslint (eslint)

v9.17.0

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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.

Summary by Sourcery

Chores:

  • Update eslint dependency from version 9.16.0 to 9.17.0 in package.json and pnpm-lock.yaml.

@renovate renovate bot enabled auto-merge (squash) December 16, 2024 23:34
Copy link

sourcery-ai bot commented Dec 16, 2024

Reviewer's Guide by Sourcery

This is a routine dependency update PR that upgrades ESLint from version 9.16.0 to 9.17.0. The changes are automatically generated by Mend Renovate and only affect the package.json and pnpm-lock.yaml files. The update includes direct changes to the ESLint dependency and related transitive dependency updates.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Update ESLint dependency version
  • Bump ESLint version from 9.16.0 to 9.17.0
  • Update related ESLint package dependencies to match the new version
package.json
pnpm-lock.yaml

Possibly linked issues


Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time. You can also use
    this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!

Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/[email protected] Transitive: environment, eval, filesystem, shell, unsafe +84 10.7 MB eslintbot, openjsfoundation

🚮 Removed packages: npm/[email protected]

View full report↗︎

@renovate renovate bot merged commit 436b249 into main Dec 16, 2024
13 checks passed
@renovate renovate bot deleted the renovate/eslint-monorepo branch December 16, 2024 23:36
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