Skip to content

build(deps-dev): bump the eslint group with 2 updates #2112

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

Open
dependabot wants to merge 1 commit into
base: master
Choose a base branch
from

build(deps-dev): bump the eslint group with 2 updates

6cc15f3
Select commit
Loading
Failed to load commit list.
Open

build(deps-dev): bump the eslint group with 2 updates #2112

build(deps-dev): bump the eslint group with 2 updates
6cc15f3
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Feb 17, 2026 in 0s

1 potential rule

Rule: automatic merge for Dependabot pull requests (merge)

  • any of: [🛡 GitHub repository ruleset rule master]
    • check-neutral = build
    • check-skipped = build
    • check-success = build
  • any of: [🛡 GitHub repository ruleset rule master]
    • check-neutral = size
    • check-skipped = size
    • check-success = size
  • any of: [🛡 GitHub repository ruleset rule master]
    • check-neutral = lint
    • check-skipped = lint
    • check-success = lint
  • any of: [🛡 GitHub repository ruleset rule master]
    • check-neutral = unit
    • check-skipped = unit
    • check-success = unit
  • #review-threads-unresolved = 0 [🛡 GitHub repository ruleset rule master]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • author=dependabot[bot]
  • title~=^build\(deps-dev\): bump
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub repository ruleset rule master]
    • check-success = commitlint
    • check-neutral = commitlint
    • check-skipped = commitlint
  • any of: [🛡 GitHub repository ruleset rule master]
    • check-success = integration (chromium)
    • check-neutral = integration (chromium)
    • check-skipped = integration (chromium)
  • any of: [🛡 GitHub repository ruleset rule master]
    • check-success = integration (firefox)
    • check-neutral = integration (firefox)
    • check-skipped = integration (firefox)
  • any of: [🛡 GitHub repository ruleset rule master]
    • check-success = integration (webkit)
    • check-neutral = integration (webkit)
    • check-skipped = integration (webkit)
  • any of: [🛡 GitHub repository ruleset rule master]
    • check-success = codecov/patch
    • check-neutral = codecov/patch
    • check-skipped = codecov/patch
  • any of: [🛡 GitHub repository ruleset rule master]
    • check-success = codecov/project
    • check-neutral = codecov/project
    • check-skipped = codecov/project
Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

View more details on Mergify