Update dependency tailwind-variants to v3.3.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
tailwind-variants	3.2.2 → 3.3.1

---

Release Notes

heroui-inc/tailwind-variants (tailwind-variants)

v3.3.1

Compare Source

Bug Fixes

• slots shared-state contamination (#​305) (8b7f0b6)

v3.3.0

Compare Source

3.2.1 (2025-11-22)

Bug Fixes

• update cn function type and import cx from tailwind-variants/lite (#​285) (3a3afce)

---

Configuration

📅 Schedule: (in timezone America/Los_Angeles)

• Branch creation
  • Only on Monday (* * * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[cloudflare-workers-and-pages]

Deploying mouseterm with    Cloudflare Pages

Latest commit:	b473f47
Status:	✅  Deploy successful!
Preview URL:	https://85229ad9.mouseterm.pages.dev
Branch Preview URL:	https://renovate-tailwind-variants-3.mouseterm.pages.dev

View logs

[dormouse-bot]

Reviewing as a draft — flagging anything that looks worth a quick fix. Mark ready for a full review.

Build & Test is red on the Dependency disclosure is current step: website/src/data/dependencies-npm.json still records tailwind-variants at 3.2.2, so the regenerated snapshot diverges from the lockfile. Renovate cannot run that generator, so the fix has to be pushed to the branch — I'm doing that now (same as #587, where the cargo disclosure needed the same follow-up commit).

The bump itself reads clean. Two lockfile changes beyond the version are upstream metadata, not regressions: engines tightens to node: '>=16.9.x' (the repo pins Node via devEngines.runtime well above that), and tailwindcss moves from a hard dependency of tailwind-variants to an optional peer — every workspace that consumes tv() already declares tailwindcss directly, and the lockfile still resolves it to 4.3.3. Leaving the ^3.2.2 specifier in the three package.json files untouched is what rangeStrategy: update-lockfile asks for.

Holding approval regardless of the CI fix: GitHub does not accept an approval on a draft.