chore(deps-dev): bump tailwindcss from 3.4.19 to 4.2.1#15
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
chore(deps-dev): bump tailwindcss from 3.4.19 to 4.2.1#15dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss) from 3.4.19 to 4.2.1. - [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.2.1/packages/tailwindcss) --- updated-dependencies: - dependency-name: tailwindcss dependency-version: 4.2.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
1 issue found across 1 file
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="package.json">
<violation number="1" location="package.json:65">
P0: **Breaking change**: This bumps Tailwind CSS from v3 to v4, a major version with extensive breaking changes, but no migration steps were applied. The build will fail because:
- `postcss.config.js` still references `tailwindcss` as the PostCSS plugin, but v4 requires the separate `@tailwindcss/postcss` package (not installed)
- `tailwind.config.js` uses the v3 JS config format (`module.exports`, `content`, `theme.extend`, `plugins: [require('tailwindcss-animate')]`), which v4 replaced with CSS-first configuration (`@theme` directives)
- `tailwindcss-animate` ^1.0.7 uses the v3 plugin API, incompatible with v4
Per the [official upgrade guide](https://tailwindcss.com/docs/upgrade-guide), you should run `npx @tailwindcss/upgrade` to automate most migration, or revert to v3 until the project is ready to migrate.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| "postcss": "^8.4.35", | ||
| "prettier": "^3.2.0", | ||
| "tailwindcss": "^3.4.1", | ||
| "tailwindcss": "^4.2.1", |
There was a problem hiding this comment.
P0: Breaking change: This bumps Tailwind CSS from v3 to v4, a major version with extensive breaking changes, but no migration steps were applied. The build will fail because:
postcss.config.jsstill referencestailwindcssas the PostCSS plugin, but v4 requires the separate@tailwindcss/postcsspackage (not installed)tailwind.config.jsuses the v3 JS config format (module.exports,content,theme.extend,plugins: [require('tailwindcss-animate')]), which v4 replaced with CSS-first configuration (@themedirectives)tailwindcss-animate^1.0.7 uses the v3 plugin API, incompatible with v4
Per the official upgrade guide, you should run npx @tailwindcss/upgrade to automate most migration, or revert to v3 until the project is ready to migrate.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At package.json, line 65:
<comment>**Breaking change**: This bumps Tailwind CSS from v3 to v4, a major version with extensive breaking changes, but no migration steps were applied. The build will fail because:
- `postcss.config.js` still references `tailwindcss` as the PostCSS plugin, but v4 requires the separate `@tailwindcss/postcss` package (not installed)
- `tailwind.config.js` uses the v3 JS config format (`module.exports`, `content`, `theme.extend`, `plugins: [require('tailwindcss-animate')]`), which v4 replaced with CSS-first configuration (`@theme` directives)
- `tailwindcss-animate` ^1.0.7 uses the v3 plugin API, incompatible with v4
Per the [official upgrade guide](https://tailwindcss.com/docs/upgrade-guide), you should run `npx @tailwindcss/upgrade` to automate most migration, or revert to v3 until the project is ready to migrate.</comment>
<file context>
@@ -62,7 +62,7 @@
"postcss": "^8.4.35",
"prettier": "^3.2.0",
- "tailwindcss": "^3.4.1",
+ "tailwindcss": "^4.2.1",
"tailwindcss-animate": "^1.0.7",
"tsx": "^4.7.0",
</file context>
Suggested change
| "tailwindcss": "^4.2.1", | |
| "tailwindcss": "^3.4.1", |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps tailwindcss from 3.4.19 to 4.2.1.
Release notes
Sourced from tailwindcss's releases.
... (truncated)
Changelog
Sourced from tailwindcss's changelog.
... (truncated)
Commits
1dce64e4.2.1 (#19714)d15d92cAllow trailing dash in functional utility names (#19696)1b164114.2.0 (#19695)6118f4fFix/misc docs and tests (#19652)5a4a7ebfix(canonicalize): prevent collapse cache pollution across calls (#19675)d0a5612Add mauve, olive, mist, and taupe color palettes (#19627)d9fff9fdocs: update package README CI badge to main (#19692)ed52d3efeat: handle backslash in@utilityname (#19626)6eb3b32Allow multiples of.25inaspect-*fractions (#19688)8ed67bfFix Tailwind CSS package README GitHub links (#19644)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for tailwindcss since your current version.
You can trigger a rebase of this PR 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 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)Summary by cubic
Upgrade tailwindcss from 3.4.19 to 4.2.1 to adopt Tailwind v4 features and fixes, including new color palettes and logical property utilities. This is a major update and may require config and utility changes.
Written for commit 95c32af. Summary will update on new commits.