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 devdependency eslint to v9.15.0 #1481

Closed
wants to merge 2 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 15, 2024

This PR contains the following updates:

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

Release Notes

eslint/eslint (eslint)

v9.15.0

Compare Source


Configuration

📅 Schedule: 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.

Copy link
Contributor Author

renovate bot commented Nov 15, 2024

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@renovate renovate bot enabled auto-merge (squash) November 15, 2024 22:36
Copy link

coderabbitai bot commented Nov 15, 2024

Important

Review skipped

Ignore keyword(s) in the title.

⛔ Ignored keywords (1)
  • chore(deps)

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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

Copy link

socket-security bot commented Nov 15, 2024

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

Package New capabilities Transitives Size Publisher
npm/@iconify-json/[email protected] None +1 1.06 MB cyberalien
npm/@iconify-json/[email protected] None +1 89.3 kB cyberalien
npm/@iconify-json/[email protected] None +1 1.96 MB cyberalien
npm/@nuxt/[email protected] filesystem Transitive: environment, eval, network +28 9.55 MB farnabaz
npm/@nuxt/[email protected] environment, network Transitive: filesystem +30 10 MB antfu
npm/@nuxt/[email protected] Transitive: environment, filesystem +10 3.36 MB danielroe
npm/@nuxt/[email protected] environment Transitive: filesystem +7 1.71 MB danielroe
npm/@nuxt/[email protected] network Transitive: environment, filesystem, unsafe +71 35.5 MB harlan_zw
npm/@nuxt/[email protected] Transitive: environment, filesystem +7 1.68 MB danielroe
npm/@nuxtjs/[email protected] Transitive: environment, filesystem +7 1.63 MB danielroe
npm/@nuxtjs/[email protected] Transitive: environment, filesystem +8 1.64 MB danielroe
npm/@nuxtjs/[email protected] Transitive: environment, filesystem, network +8 1.65 MB johannschopplich
npm/@nuxtjs/[email protected] Transitive: environment, eval, filesystem, network +23 12.8 MB danielroe
npm/@nuxtjs/[email protected] environment Transitive: filesystem +7 1.6 MB danielroe
npm/@playwright/[email protected] None 0 25.5 kB dgozman-ms, mxschmitt, pavelfeldman, ...1 more
npm/@sanity/[email protected] Transitive: environment, filesystem, unsafe +122 19.8 MB sanity-io
npm/@sanity/[email protected] Transitive: environment +30 13.9 MB ash
npm/@types/[email protected] None +2 1.69 MB types
npm/@unhead/[email protected] environment +2 202 kB harlan_zw
npm/@unocss/[email protected] Transitive: environment, filesystem +37 5.41 MB antfu, unocss-bot
npm/@unocss/[email protected] None +4 1.48 MB antfu
npm/@unocss/[email protected] None 0 44 kB antfu
npm/@vue/[email protected] eval 0 1.51 MB lmiller1990

🚮 Removed packages: npm/[email protected]

View full report↗︎

Copy link

cloudflare-workers-and-pages bot commented Nov 17, 2024

Deploying danielroe with  Cloudflare Pages  Cloudflare Pages

Latest commit: e53e6f4
Status:🚫  Build failed.

View logs

@renovate renovate bot force-pushed the renovate/all-linters branch 3 times, most recently from 00b1888 to 68fa727 Compare November 18, 2024 12:08
Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteCI
Possible typosquat attack npm/[email protected] ⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

Copy link
Contributor Author

renovate bot commented Nov 20, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@danielroe danielroe closed this Nov 23, 2024
auto-merge was automatically disabled November 23, 2024 23:31

Pull request was closed

Copy link
Contributor Author

renovate bot commented Nov 23, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (9.15.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/all-linters branch November 23, 2024 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant