Skip to content

chore(deps): update tailwindcss monorepo to v4.3.1#136

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/tailwindcss-monorepo
Closed

chore(deps): update tailwindcss monorepo to v4.3.1#136
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/tailwindcss-monorepo

Conversation

@renovate

@renovate renovate Bot commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@tailwindcss/postcss (source) 4.3.04.3.1 age confidence
tailwindcss (source) 4.3.04.3.1 age confidence

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: (UTC)

  • Branch creation
    • "before 4am"
  • 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 these updates again.


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

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

@netlify

netlify Bot commented Jun 13, 2026

Copy link
Copy Markdown

Deploy Preview for semantic-template failed. Why did it fail? →

Name Link
🔨 Latest commit 25faf3c
🔍 Latest deploy log https://app.netlify.com/projects/semantic-template/deploys/6a2ca9468ba75600086d2bba

@happy-haki

Copy link
Copy Markdown
Contributor

Maintainer check 2026-06-14: holding this PR. It updates tailwindcss/@tailwindcss-postcss to 4.3.1, published 2026-06-12T17:59Z, so it does not satisfy the 7-day npm age rule yet (current cutoff: 2026-06-07T00:30Z). Netlify deploy-preview checks are also failing. Will revisit after the age window and green checks.

@coauthors

coauthors Bot commented Jun 14, 2026

Copy link
Copy Markdown

People can be co-author:

Candidate Reasons Count Add this as commit message
@happy-haki #136 (comment) #136 (comment) #136 (comment) 3 Co-authored-by: happy-haki <266456141+happy-haki@users.noreply.github.com>

@happy-haki

Copy link
Copy Markdown
Contributor

Maintainer cleanup: closing this Renovate dependency PR instead of merging now. The target package version is still younger than the repo's 7-day dependency-age policy and/or its preview checks are not clean. Main currently passes local install/check/build, so keeping the repo green and PR queue empty. Renovate can propose a fresh update after the version has aged or a newer qualifying version exists.

@happy-haki

Copy link
Copy Markdown
Contributor

Closing during maintainer cleanup to keep PR queue at 0 while preserving build stability. Target update is not eligible for merge under the 7-day dependency-age policy and/or has failing preview checks.

@happy-haki happy-haki closed this Jun 14, 2026
@renovate

renovate Bot commented Jun 14, 2026

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (4.3.1). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate Bot deleted the renovate/tailwindcss-monorepo branch June 14, 2026 09:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant