-
Notifications
You must be signed in to change notification settings - Fork 0
chore(deps-dev): bump tailwindcss from 3.4.18 to 4.1.16 #28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Needs ReviewI recommend reviewing this upgrade before merging because this is a major version upgrade from v3 to v4 that introduces significant breaking changes requiring manual configuration updates. The project uses Tailwind CSS v3 configuration syntax which is incompatible with v4's new CSS-first configuration system. Specifically, the tailwind.config.js uses the legacy v3 module.exports format, src/index.css uses deprecated @tailwind directives that must be replaced with @import syntax, and postcss.config.js uses the legacy plugin configuration. While the codebase doesn't use any of the removed deprecated utilities (max-w-auto, break-words, clip, etc.), the configuration files must be migrated to v4 syntax before the build will work. The security vulnerabilities mentioned (CVE-2024-4068, CVE-2024-4067) in transitive dependencies braces and micromatch are not relevant to this upgrade as they were already fixed in earlier v4 versions. What we checked
Dependency UsageNo direct usages found in your codebase. ChangesA major upgrade to Tailwind CSS v4 brings critical breaking changes including removal of invalid
View 616 more changes
References (7)[1]: Upgrading tailwindcss from v3.4.18 to v4.1.16 - a major version change with breaking configuration syntax kcd-showcase-trw-demo-app/package.json Line 44 in 6cdb279
[2]: Uses v3 configuration syntax (module.exports) which must be converted to v4 CSS-first configuration or @config directive
[3]: Uses deprecated @tailwind directives which must be replaced with @import 'tailwindcss' in v4
[4]: Uses legacy PostCSS plugin configuration 'tailwindcss: {}' which needs to be updated for v4 compatibility
[5]: Official v4 upgrade guide documents breaking changes: CSS-first configuration replaces JS config, @import replaces @tailwind directives, and requires Safari 16.4+ and Chrome 111+ (source link) [6]: Community reports v4 removes default element styles and dark mode functionality, requiring manual fixes in migrated projects (source link) [7]: Uses shadow-xl utility - confirmed safe as Tailwind v4 only deprecated shadow-inner, not shadow-xl
fossabot analyzed this PR using dependency research. |
Bumps [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss) from 3.4.18 to 4.1.16. - [Release notes](https://github.com/tailwindlabs/tailwindcss/releases) - [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md) - [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.1.16/packages/tailwindcss) --- updated-dependencies: - dependency-name: tailwindcss dependency-version: 4.1.16 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
6cdb279 to
4994239
Compare
|
Looks like tailwindcss is no longer being updated by Dependabot, so this is no longer needed. |
Bumps tailwindcss from 3.4.18 to 4.1.16.
Release notes
Sourced from tailwindcss's releases.
... (truncated)
Changelog
Sourced from tailwindcss's changelog.
... (truncated)
Commits
cbbbe84Release 4.1.16 (#19185)601d671Fix incorrect colors used in pseudo-element (#19184)a41add9Improve canonicalization for& > :pseudoand& :pseudoarbitrary variants...0113b88Fix canonicalization of arbitrary variants with attribute selectors (#19176)29687e0Discard candidates with an empty data type (#19172)56e7f3bImprove memory usage during canonicalization (#19171)3a4ab82Stop suggesting legacy utilities (#19169)7537e34Ignore--tw-variables during internal signature computation (#19156)66c18caCollapse multiple utilities (#19147)b2e2435Release 4.1.15 (#19159)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)