Skip to content

build(deps): bump node-forge from 1.3.1 to 1.3.2

eac8423
Select commit
Loading
Failed to load commit list.
Open

build(deps): bump node-forge from 1.3.1 to 1.3.2 #1008

build(deps): bump node-forge from 1.3.1 to 1.3.2
eac8423
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Nov 26, 2025 in 0s

3 potential rules

Rule: Auto Squash and Merge (delete_head_branch)

  • closed [📌 delete_head_branch requirement]
  • label=ready to squash and merge
  • base=master
  • status-success=ci

Rule: Auto Rebase and Merge (delete_head_branch)

  • closed [📌 delete_head_branch requirement]
  • label=ready to rebase and merge
  • base=master
  • status-success=ci

Rule: Auto Rebase and Merge + Auto Squash and Merge (queue)

  • any of: [🔀 queue conditions]
    • all of: [📌 queue conditions of queue duplicated default from Auto Rebase and Merge]
      • label=ready to rebase and merge
      • base=master
      • status-success=ci
    • all of: [📌 queue conditions of queue duplicated default from Auto Squash and Merge]
      • label=ready to squash and merge
      • base=master
      • status-success=ci
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of: [📌 queue -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

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