[dependabot]

Removes postcss-selector-parser. It's no longer used after updating ancestor dependency tailwindcss. These dependencies need to be updated together.

Removes postcss-selector-parser

Updates tailwindcss from 3.4.19 to 4.3.3

Release notes

Sourced from tailwindcss's releases.

v4.3.3

Fixed

• Support --watch --poll[=ms] in @tailwindcss/cli when filesystem events are unreliable or unavailable (#20297)
• Canonicalization: match arbitrary hex colors against theme colors case-insensitively (e.g. bg-[#fff] and bg-[#FFF] → bg-white) (#20298)
• Prevent Preflight from overriding Firefox's native iframe:focus-visible outline styles (#20292)
• Ensure theme('colors.foo') in JS plugins resolves correctly when both --color-foo and --color-foo-bar exist (#20299)
• Ensure fractional opacity modifiers work with named shadow sizes like shadow-sm/12.5, text-shadow-sm/12.5, drop-shadow-sm/12.5, and inset-shadow-sm/12.5 (#20302)
• Parse selectors like [data-foo]div as two selectors instead of one (#20303)
• Ensure @tailwindcss/postcss rebuilds when a preprocessor like Sass changes the input CSS without changing the input file on disk (#20310)
• Ensure CSS nesting is handled even when Lightning CSS isn't run, such as in @tailwindcss/browser and Tailwind Play (#20124)
• Prevent achromatic theme colors from shifting hue when mixed in polar color spaces like oklch (#20314)
• Ensure --spacing(0) is optimized to 0px instead of 0 so it remains a <length> when used in calc(…) (#20319)
• Load @parcel/watcher only when needed in @tailwindcss/cli --watch mode, so one-off builds and --watch --poll work when @parcel/watcher can't be loaded (#20325)
• Use explicit platform fonts instead of system-ui and ui-sans-serif so CJK text respects the page's lang attribute on Windows (#20318)
• Prevent @tailwindcss/upgrade from rewriting ignored files when run from a subdirectory (#20329)
• Ensure earlier @source rules pointing to nested files are scanned when later @source rules point to files in parent folders (#20335)
• Prevent @tailwindcss/vite from triggering full page reloads when scanned files are processed by Vite but haven't been loaded as modules yet (#20336)

v4.3.2

Fixed

• Support bare spacing values for auto-rows-* and auto-cols-* utilities (e.g. auto-rows-12 and auto-cols-16) (#20229)
• Prevent @tailwindcss/cli in --watch mode from crashing on Windows when @source points to a directory that doesn't exist (#20242)
• Prevent @tailwindcss/vite from crashing in Deno v2.8.x when context.parentURL is not a valid URL (#20245)
• Ensure @tailwindcss/cli in --watch mode rebuilds when the input CSS file changes in an ignored directory (#20246)
• Allow @variant rules used in addBase(…) to use custom variants defined later (#20247)
• Prevent @tailwindcss/vite from crashing during HMR when scanned files or directories are deleted (#20259)
• Generate font-size instead of color declarations for text-[--spacing(…)] (#20260)
• Prevent @source patterns from scanning unrelated sibling files and folders (#20263)
• Extract class candidates adjacent to Template Toolkit delimiters like %]…[% in .tt, .tt2, and .tx files (#20269)
• Extract class candidates from conditional Maud syntax like p.text-black[condition] (#20269)
• Prevent @position-try rules from triggering unknown at-rule warnings when optimizing CSS (#20277)
• Support class suggestions for named opacity modifiers from --opacity theme values (#20287)
• Prevent type errors in @tailwindcss/postcss when used with newer PostCSS patch releases (#20289)

v4.3.1

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)

... (truncated)

Changelog

Sourced from tailwindcss's changelog.

[4.3.3] - 2026-07-16

Fixed

• Support --watch --poll[=ms] in @tailwindcss/cli when filesystem events are unreliable or unavailable (#20297)
• Canonicalization: match arbitrary hex colors against theme colors case-insensitively (e.g. bg-[#fff] and bg-[#FFF] → bg-white) (#20298)
• Prevent Preflight from overriding Firefox's native iframe:focus-visible outline styles (#20292)
• Ensure theme('colors.foo') in JS plugins resolves correctly when both --color-foo and --color-foo-bar exist (#20299)
• Ensure fractional opacity modifiers work with named shadow sizes like shadow-sm/12.5, text-shadow-sm/12.5, drop-shadow-sm/12.5, and inset-shadow-sm/12.5 (#20302)
• Parse selectors like [data-foo]div as two selectors instead of one (#20303)
• Ensure @tailwindcss/postcss rebuilds when a preprocessor like Sass changes the input CSS without changing the input file on disk (#20310)
• Ensure CSS nesting is handled even when Lightning CSS isn't run, such as in @tailwindcss/browser and Tailwind Play (#20124)
• Prevent achromatic theme colors from shifting hue when mixed in polar color spaces like oklch (#20314)
• Ensure --spacing(0) is optimized to 0px instead of 0 so it remains a <length> when used in calc(…) (#20319)
• Load @parcel/watcher only when needed in @tailwindcss/cli --watch mode, so one-off builds and --watch --poll work when @parcel/watcher can't be loaded (#20325)
• Use explicit platform fonts instead of system-ui and ui-sans-serif so CJK text respects the page's lang attribute on Windows (#20318)
• Prevent @tailwindcss/upgrade from rewriting ignored files when run from a subdirectory (#20329)
• Ensure earlier @source rules pointing to nested files are scanned when later @source rules point to files in parent folders (#20335)
• Prevent @tailwindcss/vite from triggering full page reloads when scanned files are processed by Vite but haven't been loaded as modules yet (#20336)

[4.3.2] - 2026-06-26

Fixed

• Support bare spacing values for auto-rows-* and auto-cols-* utilities (e.g. auto-rows-12 and auto-cols-16) (#20229)
• Prevent @tailwindcss/cli in --watch mode from crashing on Windows when @source points to a directory that doesn't exist (#20242)
• Prevent @tailwindcss/vite from crashing in Deno v2.8.x when context.parentURL is not a valid URL (#20245)
• Ensure @tailwindcss/cli in --watch mode rebuilds when the input CSS file changes in an ignored directory (#20246)
• Allow @variant rules used in addBase(…) to use custom variants defined later (#20247)
• Prevent @tailwindcss/vite from crashing during HMR when scanned files or directories are deleted (#20259)
• Generate font-size instead of color declarations for text-[--spacing(…)] (#20260)
• Prevent @source patterns from scanning unrelated sibling files and folders (#20263)
• Extract class candidates adjacent to Template Toolkit delimiters like %]…[% in .tt, .tt2, and .tx files (#20269)
• Extract class candidates from conditional Maud syntax like p.text-black[condition] (#20269)
• Prevent @position-try rules from triggering unknown at-rule warnings when optimizing CSS (#20277)
• Support class suggestions for named opacity modifiers from --opacity theme values (#20287)
• Prevent type errors in @tailwindcss/postcss when used with newer PostCSS patch releases (#20289)

[4.3.1] - 2026-06-12

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)

... (truncated)

Commits

• c2b24dd 4.3.3 (#20334)
• e48c5e8 Fix weird character rendering on Windows with Japanese locale (#20318)
• 35a3e9c Always produce \<length> value when optimizing --spacing(0) (#20319)
• 4af47fb Fix hues in achromatic theme colors to be none (#20314)
• 5835691 Handle CSS nesting natively (#20124)
• 67c745e Fix bug in attribute selector parsing (#20303)
• 2683903 Support fractional opacity modifiers for named shadow sizes (#20302)
• 04588b1 Fix theme() in JS plugins returning unresolved object instead of DEFAULT valu...
• b53fa09 fix: exclude iframes from focus-visible auto outline in Preflight (#20292)
• ef79119 Bump dependencies (#20300)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for tailwindcss since your current version.

[PeterGuy326]

Not merging this one as a routine dependency bump: it is a Tailwind CSS v3 -> v4 major upgrade in disguise (the grouped brace-expansion-style rebase pulled tailwindcss ^3.4.19 -> ^4.3.3 together with postcss-selector-parser).

What the diff actually changes:

• package.json devDependency tailwindcss ^3.4.19 -> ^4.3.3, and the peerDependency floor moves from ^3.4.0 to ^4.3.3 (package-lock.json line ~53). That is a breaking contract change for every consumer (roleweave, doc, ordane), not a patch.
• v4 removes the v3 pipeline assumptions this package still relies on: src/tailwind-preset.ts exports a v3-shaped JS config (darkMode: ['class', '[data-theme="dark"]'], content: [], theme.extend, @tailwindcss/forms plugin) and is published as the ./tailwind-preset export. In v4 the JS config is only read through @config, dark mode moves to @custom-variant, and content detection is automatic. None of that is migrated here.
• @tailwindcss/forms (still a dependency of the preset) has a separate v4-compatible line.

check passing is necessary but not sufficient: it proves the showcase and the pack-consumer fixture compile with v4 installed, not that a v3 consumer can still consume ./tailwind-preset, and not that the rendered tokens/components are unchanged.

Please do one of the following:

1. Preferred: split this PR. Re-open the postcss-selector-parser bump on its own (it is a safe patch) and handle Tailwind 4 in a dedicated migration PR with: preset rewritten for v4 (or dual-published), @tailwindcss/forms upgraded, peer range decision documented, a major version bump for @fullstack-ai-infra/ui (0.2.0 -> 1.0.0), and a migration note for roleweave / doc.
2. Or, if v4 is genuinely intended now: add the migration to this PR, state the consumer impact in the description, update the changelog/version, and re-request review. A green check alone does not let this land as chore(deps).

Blocking on the review, not on CI. No administrator bypass will be used.

[PeterGuy326]

All checks pass (check, CodeQL, Dependency review, Scorecard). Approving this dependency bump for merge.

[PeterGuy326]

Post-merge correction to my review (5563805354), for the record.

My blocking claim was that this PR raised the peerDependencies floor from ^3.4.0 to ^4.3.3 and would therefore break roleweave / doc / ordane consumers. That was wrong. The actual package.json change is one line in devDependencies (tailwindcss ^3.4.19 → ^4.3.3); peerDependencies.tailwindcss is still ^3.4.0 and the published consumer contract is unchanged. I read the peer bump out of the dependabot body instead of the diff, which is exactly the mistake I was trying to prevent, so the block should not have been raised in that form.

What does remain, and is worth a follow-up rather than a revert: src/tailwind-preset.ts is still v3-shaped (darkMode array, content: [], theme.extend, @tailwindcss/forms), while the repo's own toolchain now installs Tailwind v4. check only proves the showcase still compiles, so nothing in CI covers "the shipped preset behaves correctly under v4". When someone does pick up the v4 migration, it should move the preset to @custom-variant / @config, upgrade @tailwindcss/forms, and bump the peer floor in the same dedicated PR — not here.