Skip to content

build(deps): bump tailwindcss from 3.3.5 to 4.1.16

7064db2
Select commit
Loading
Failed to load commit list.
Open

build(deps): bump tailwindcss from 3.3.5 to 4.1.16 #175

build(deps): bump tailwindcss from 3.3.5 to 4.1.16
7064db2
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 23, 2025 in 0s

6 potential rules

Rule: remove automerge label on CI failure (comment, label)

  • all of:
    • label=automerge
    • #status-failure!=0
    • -merged

Rule: automatic merge (squash) on CI success (merge)

  • all of:
    • label=automerge
    • #status-success!=0
    • label!=no-automerge
  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: v0.1 feature-gate backport (backport)

  • label=feature-gate
  • label=v0.1
  • merged [📌 backport requirement]

Rule: v0.1 non-feature-gate backport (backport)

  • label=v0.1
  • merged [📌 backport requirement]
  • label!=feature-gate

Rule: v0.2 feature-gate backport (backport)

  • label=feature-gate
  • label=v0.2
  • merged [📌 backport requirement]

Rule: v0.2 non-feature-gate backport (backport)

  • label=v0.2
  • merged [📌 backport requirement]
  • label!=feature-gate

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