chore(deps-dev): bump caniuse-lite from 1.0.30001760 to 1.0.30001762

[dependabot]

Bumps caniuse-lite from 1.0.30001760 to 1.0.30001762.

Commits

• 011fa7c Update caniuse-db 1.0.30001762
• 59e2d41 Update caniuse-db 1.0.30001761
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Required Reviews

Wonderful, this rule succeeded.

• any of:
  • author = dependabot[bot]
  • #approved-reviews-by >= 2

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

🟢 🔎 Reviews

Wonderful, this rule succeeded.

• #changes-requested-reviews-by = 0
• #review-requested = 0
• #review-threads-unresolved = 0

🟢 📕 PR description

Wonderful, this rule succeeded.

• body ~= (?ms:.{48,})

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for fe0cf6a.

🟢 All jobs passed!

But CI Insights is watching 👀

[mergify]

Merge Queue Status

Rule: automated updates

---

• ✅ Entered queue — 2026-02-09 10:01 UTC
• ✅ Checks started · on draft merge queue: embarking main (ba3ac97), #171, #173, #172, #174, #162, #160, #169 and [#166 + #175 + #170] together #186
• 🚫 Left the queue — 2026-02-09 10:10 UTC · at fe0cf6a338942a54544bbb1a3c2c2d21fbe134d2

This pull request spent 8 minutes 38 seconds in the queue, including 2 minutes 21 seconds running CI.

Reason

Pull request #170 has been dequeued. Mergify failed to merge the pull request. GitHub can't merge the pull request after 14 retries.
Base branch was modified in the meantime

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

[dependabot]

Superseded by #189.