Skip to content
This repository has been archived by the owner on Aug 21, 2024. It is now read-only.

chore(deps-dev): bump @types/node from 20.14.10 to 20.14.11 #1817

Merged
merged 1 commit into from
Jul 17, 2024

chore(deps-dev): bump @types/node from 20.14.10 to 20.14.11

b6d5c17
Select commit
Loading
Failed to load commit list.
Merged

chore(deps-dev): bump @types/node from 20.14.10 to 20.14.11 #1817

chore(deps-dev): bump @types/node from 20.14.10 to 20.14.11
b6d5c17
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Jul 17, 2024 in 0s

1 potential rule

Rule: Automatic merge on approval (merge)

  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • author~=^dependabot(|-preview)\[bot\]$
  • check-success=build
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success=Configuration changed
  • any of: [🛡 GitHub branch protection]
    • check-success=build
    • check-neutral=build
    • check-skipped=build

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


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