fix(deps): update tailwindcss monorepo (4.3.0 → 4.3.1)

[its-miso]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@tailwindcss/postcss (source)	4.3.0 → 4.3.1
tailwindcss (source)	4.3.0 → 4.3.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

tailwindlabs/tailwindcss (@​tailwindcss/postcss)

v4.3.1

Compare Source

Added

• Add --silent option to suppress output in @tailwindcss/cli (#​20100)

Fixed

• Remove deprecation warnings by using Module#registerHooks instead of Module#register on Node 26+ (#​20028)
• Canonicalization: don't crash when plugin utilities throw for unsupported values (#​20052)
• Allow @apply to be used with CSS mixins (#​19427)
• Ensure not-* correctly negates @container queries, including style(…) queries (#​20059)
• Ensure drop-shadow-* color utilities work with custom shadow values containing calc(…) (#​20080)
• Fix 'Sourcemap is likely to be incorrect' warnings when using @tailwindcss/vite (#​20103)
• Ensure @tailwindcss/webpack can be installed in Rspack projects without requiring webpack as a peer dependency (#​20027)
• Canonicalization: don't suggest invalid calc(…) expressions (e.g. px-[calc(1rem+0px)] → px-[calc(1rem+0)]) (#​20127)
• Canonicalization: avoid suggesting large spacing-scale values for arbitrary lengths (e.g. left-[99999px] → left-[99999px], not left-24999.75) (#​20130)
• Ensure @tailwindcss/cli in --watch mode recovers when a tracked dependency is deleted and restored (#​20137)
• Ensure standalone @tailwindcss/cli binaries are ignored when scanning for class candidates (#​20139)
• Ensure class candidates are extracted from Twig addClass(…) and removeClass(…) calls (#​20198)
• Don't crash in the Ruby or Vue preprocessors when scanning files containing invalid UTF-8 bytes (#​19588)
• Allow @variant to be used inside addBase (#​19480)
• Ensure @source globs with symlinks are preserved (#​20203)
• Ensure later @source rules can re-include files excluded by earlier @source not rules (#​20203)
• Upgrade: don't migrate empty class rules to invalid @utility rules (#​20205)
• Ensure transitions between inset-shadow-none and other inset shadows work correctly (#​20208)
• Ensure explicitly referenced @source directories are scanned even when ignored by git (#​20214)
• Ensure @source globs ending in **/* preserve dynamic path segments to avoid scanning too many files (#​20217)
• Canonicalization: don't fold calc(…) divisions when the result would require high precision (e.g. w-[calc(100%/3.5)] → w-[calc(100%/3.5)], not w-[28.571428571428573%]) (#​20221)
• Serve ESM type declarations to ESM importers of @tailwindcss/postcss (#​20228)

Changed

• Generate 0 instead of calc(var(--spacing) * 0) for spacing utilities like m-0 and left-0 (#​20196)
• Generate var(--spacing) instead of calc(var(--spacing) * 1) for spacing utilities like m-1 and left-1 (#​20196)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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

---

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

---

This PR has been generated by Renovate Bot.

Superseded by a newer automated review for this pull request.

Superseded by a newer automated review for this pull request.

Superseded by a newer automated review for this pull request.

[its-saffron]

AI Automated Review

Full PR review.

Analysis engine: MiniMax-M2.7@https://litellm.jory.dev/v1 (anthropic) — escalated (fast_low_confidence)

PR Review: tailwindcss monorepo update (4.3.0 → 4.3.1)

Summary

This PR updates the Tailwind CSS monorepo packages from v4.3.0 to v4.3.1. The update is a patch version bump with no breaking API changes.

---

Required Checks

✅ check for breaking API changes in updated dependencies

Verified through the v4.3.1 release notes from the GitHub Releases Enrichment data. The release contains:

• Bug fixes: Canonicalization fixes, container query fixes, shadow utilities, sourcemap warnings, and Node 26+ deprecation warning removal
• New features: --silent CLI option, @apply with CSS mixins support
• CSS generation optimizations: Changed calc(var(--spacing) * 0) to 0 and calc(var(--spacing) * 1) to var(--spacing) for spacing utilities

None of these changes constitute breaking API changes. The CSS output optimizations are internal implementation details that don't affect the CSS class API. The update maintains backward compatibility with existing Tailwind usage patterns in the codebase.

✅ run full test suite after upgrade

CI has validated this PR through the "Validate" check, which according to AGENTS.md runs npm run lint, npm run typecheck, npm run test, and npm run build. All three CI checks (review, Docker Build, Validate) completed with success status.

---

Standards Compliance

• Patch version bump: The semver bump from 4.3.0 → 4.3.1 is appropriate for a patch release containing only bug fixes and internal optimizations
• Lock file only: Only package-lock.json was modified, as expected for a dependency update
• CI validation: All repository-required validation checks passed

---

Linked Issue Fit

No linked issue was provided, so no specific acceptance criteria need to be verified against the PR.

---

Evidence Provider Findings

Not applicable — no evidence providers are configured for this repository.

---

Tool Harness Findings

Not applicable — no tool harness findings were produced.

---

Unknowns / Needs Verification

None identified. The release notes are complete, CI validation passed, and the change is a straightforward patch version update with no breaking changes.

---

Recommendation

Approve. This is a low-risk patch version update of a dev dependency with no breaking changes. The CI pipeline has validated the upgrade through lint, typecheck, tests, and build checks. The update brings bug fixes including Node 26+ compatibility improvements and canonicalization fixes that will improve build consistency.