build(deps): bump tailwindcss from 4.1.12 to 4.1.14 in /frontend

[dependabot]

Bumps tailwindcss from 4.1.12 to 4.1.14.

Release notes

Sourced from tailwindcss's releases.

v4.1.14

Fixed

• Handle ' syntax in ClojureScript when extracting classes (#18888)
• Handle @variant inside @custom-variant (#18885)
• Merge suggestions when using @utility (#18900)
• Ensure that file system watchers created when using the CLI are always cleaned up (#18905)
• Do not generate grid-column utilities when configuring grid-column-start or grid-column-end (#18907)
• Do not generate grid-row utilities when configuring grid-row-start or grid-row-end (#18907)
• Prevent duplicate CSS when overwriting a static utility with a theme key (#18056)
• Show Lightning CSS warnings (if any) when optimizing/minifying (#18918)
• Use default export condition for @tailwindcss/vite (#18948)
• Re-throw errors from PostCSS nodes (#18373)
• Detect classes in markdown inline directives (#18967)
• Ensure files with only @theme produce no output when built (#18979)
• Support Maud templates when extracting classes (#18988)
• Upgrade: Do not migrate variant = 'outline' during upgrades (#18922)
• Upgrade: Show version mismatch (if any) when running upgrade tool (#19028)
• Upgrade: Ensure first class inside className is migrated (#19031)
• Upgrade: Migrate classes inside *ClassName and *Class attributes (#19031)

v4.1.13

Changed

• Drop warning from browser build (#18731)
• Drop exact duplicate declarations when emitting CSS (#18809)

Fixed

• Don't transition visibility when using transition (#18795)
• Discard matched variants with unknown named values (#18799)
• Discard matched variants with non-string values (#18799)
• Show suggestions for known matchVariant values (#18798)
• Replace deprecated clip with clip-path in sr-only (#18769)
• Hide internal fields from completions in matchUtilities (#18820)
• Ignore .vercel folders by default (can be overridden by @source … rules) (#18855)
• Consider variants starting with @- to be invalid (e.g. @-2xl:flex) (#18869)
• Do not allow custom variants to start or end with a - or _ (#18867, #18872)
• Upgrade: Migrate aria theme keys to @custom-variant (#18815)
• Upgrade: Migrate data theme keys to @custom-variant (#18816)
• Upgrade: Migrate supports theme keys to @custom-variant (#18817)

Changelog

Sourced from tailwindcss's changelog.

[4.1.14] - 2025-10-01

Fixed

• Handle ' syntax in ClojureScript when extracting classes (#18888)
• Handle @variant inside @custom-variant (#18885)
• Merge suggestions when using @utility (#18900)
• Ensure that file system watchers created when using the CLI are always cleaned up (#18905)
• Do not generate grid-column utilities when configuring grid-column-start or grid-column-end (#18907)
• Do not generate grid-row utilities when configuring grid-row-start or grid-row-end (#18907)
• Prevent duplicate CSS when overwriting a static utility with a theme key (#18056)
• Show Lightning CSS warnings (if any) when optimizing/minifying (#18918)
• Use default export condition for @tailwindcss/vite (#18948)
• Re-throw errors from PostCSS nodes (#18373)
• Detect classes in markdown inline directives (#18967)
• Ensure files with only @theme produce no output when built (#18979)
• Support Maud templates when extracting classes (#18988)
• Upgrade: Do not migrate variant = 'outline' during upgrades (#18922)
• Upgrade: Show version mismatch (if any) when running upgrade tool (#19028)
• Upgrade: Ensure first class inside className is migrated (#19031)
• Upgrade: Migrate classes inside *ClassName and *Class attributes (#19031)

[4.1.13] - 2025-09-03

Changed

• Drop warning from browser build (#18731)
• Drop exact duplicate declarations when emitting CSS (#18809)

Fixed

• Don't transition visibility when using transition (#18795)
• Discard matched variants with unknown named values (#18799)
• Discard matched variants with non-string values (#18799)
• Show suggestions for known matchVariant values (#18798)
• Replace deprecated clip with clip-path in sr-only (#18769)
• Hide internal fields from completions in matchUtilities (#18820)
• Ignore .vercel folders by default (can be overridden by @source … rules) (#18855)
• Consider variants starting with @- to be invalid (e.g. @-2xl:flex) (#18869)
• Do not allow custom variants to start or end with a - or _ (#18867, #18872)
• Upgrade: Migrate aria theme keys to @custom-variant (#18815)
• Upgrade: Migrate data theme keys to @custom-variant (#18816)
• Upgrade: Migrate supports theme keys to @custom-variant (#18817)

Commits

• b67cbcf Prepare v4.1.14 release (#19037)
• cc8fefc Update magic-string to version 0.30.19
• 210575a Update dedent 1.6.0 → 1.7.0 (minor) (#19010)
• c6e0a55 Ensure files with only @theme produce no output when built (#18979)
• 9a5bae2 Revert "Update all pnpm dependencies (2025-09-20) (#18971)"
• 42eadfd Update all pnpm dependencies (2025-09-20) (#18971)
• c2aab49 Bump Prettier (#18960)
• d1fd645 Proposal: Allow overwriting static utilities that have a namespace (#18056)
• 340b59d Do not generate grid-column when configuring grid-column-start or `grid-c...
• b7c7e48 Add @container-size utility (#18901)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)

[jazzberry-ai]

Bug Report

Name	Severity	Example test case	Description
Potential incompatibility with @types/node update in GraphQL codegen	Medium	1. Apply the patch. 2. Run GraphQL codegen: cd /root/whodb/frontend && pnpm run graphql:codegen. 3. Inspect the generated GraphQL types (frontend/src/generated/graphql.tsx) for any type errors or inconsistencies related to the updated @types/node version.	The patch updates @types/node from 24.5.2 to 24.6.1, which is used by GraphQL codegen. This could potentially introduce type incompatibilities in the generated GraphQL types, leading to runtime errors or unexpected behavior. The @graphql-tools packages were also updated which could cause issues with graphql codegen as well.
Potential regular expression parsing issues due to regexpu-core and regjsparser updates	Low	1. Apply the patch. 2. Identify Tailwind CSS classes that use complex regular expressions, such as those involving unicode ranges or advanced features. 3. Use these classes in a component and verify that the styling is applied correctly.	The patch updates regexpu-core and regjsparser, which are used for regular expression parsing. Tailwind CSS relies on regular expressions for parsing class names. Updates to these dependencies could potentially introduce issues with how Tailwind CSS classes are parsed, leading to incorrect or missing styles.

_{Comments? Email us.}

[jazzberry-ai]

Bug Report

Name	Severity	Example test case	Description
Potential compatibility issues with @types/node update	Medium	Create a complex Node.js application that uses various features of @types/node and its dependent packages (e.g., @graphql-tools/cli, vite) and test if it works correctly.	The update to @types/node from 24.5.2 to 24.6.2 might introduce compatibility issues or break existing functionality in packages that depend on it. This could lead to unexpected errors or incorrect behavior in the frontend.
Potential browser compatibility issues	Low	Test the frontend on different browsers to see if the updates to baseline-browser-mapping, browserslist, caniuse-lite, and electron-to-chromium have introduced any regressions.	The update to baseline-browser-mapping, browserslist, caniuse-lite, and electron-to-chromium might affect the browser compatibility of the frontend, leading to rendering issues or broken functionality on certain browsers.

_{Comments? Email us.}