Skip to content

chore(deps-dev): bump js-yaml from 4.1.1 to 4.3.0#60

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/js-yaml-4.3.0
Open

chore(deps-dev): bump js-yaml from 4.1.1 to 4.3.0#60
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/js-yaml-4.3.0

chore(deps-dev): bump js-yaml from 4.1.1 to 4.3.0

b97515d
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jun 28, 2026 in 1s

2 rules match and 2 potential rules

Rule: Auto-merge dependabot updates when checks pass (merge)

  • any of: [🛡 GitHub repository ruleset rule Default]
    • check-neutral = @sonarqubecloud/SonarCloud Code Analysis
    • check-skipped = @sonarqubecloud/SonarCloud Code Analysis
    • check-success = @sonarqubecloud/SonarCloud Code Analysis
  • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule Default]
  • #review-threads-unresolved = 0 [🛡 GitHub repository ruleset rule Default]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • author=dependabot[bot]
  • github-require-last-push-approval [🛡 GitHub repository ruleset rule Default]
  • label!=wontfix
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub repository ruleset rule Default]
    • check-success = @github-actions/🧹 Lint
    • check-neutral = @github-actions/🧹 Lint
    • check-skipped = @github-actions/🧹 Lint
  • any of: [🛡 GitHub repository ruleset rule Default]
    • check-success = @github-actions/🧪 Test
    • check-neutral = @github-actions/🧪 Test
    • check-skipped = @github-actions/🧪 Test
  • any of: [🛡 GitHub repository ruleset rule Default]
    • check-success = @github-actions/🛠️ Build
    • check-neutral = @github-actions/🛠️ Build
    • check-skipped = @github-actions/🛠️ Build

✅ Rule: Auto-merge dependabot updates when checks pass (review)

  • author=dependabot[bot]
  • label!=wontfix

Rule: Auto-merge when all checks pass and the PR has been approved (merge)

  • any of: [🛡 GitHub repository ruleset rule Default]
    • check-neutral = @sonarqubecloud/SonarCloud Code Analysis
    • check-skipped = @sonarqubecloud/SonarCloud Code Analysis
    • check-success = @sonarqubecloud/SonarCloud Code Analysis
  • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule Default]
  • #approved-reviews-by>=1
  • #changes-requested-reviews-by=0
  • #review-threads-unresolved = 0 [🛡 GitHub repository ruleset rule Default]
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • github-require-last-push-approval [🛡 GitHub repository ruleset rule Default]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of: [🛡 GitHub repository ruleset rule Default]
    • check-success = @github-actions/🧹 Lint
    • check-neutral = @github-actions/🧹 Lint
    • check-skipped = @github-actions/🧹 Lint
  • any of: [🛡 GitHub repository ruleset rule Default]
    • check-success = @github-actions/🧪 Test
    • check-neutral = @github-actions/🧪 Test
    • check-skipped = @github-actions/🧪 Test
  • any of: [🛡 GitHub repository ruleset rule Default]
    • check-success = @github-actions/🛠️ Build
    • check-neutral = @github-actions/🛠️ Build
    • check-skipped = @github-actions/🛠️ Build

✅ Rule: Assign PR to its author (assign)

  • #files=1

1 not applicable rule

Rule: Ask for reviews (request_reviews)

  • -author=dependabot[bot]
  • -closed
  • -draft
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