chore(deps-dev): bump tailwindcss from 3.4.19 to 4.3.0#41
chore(deps-dev): bump tailwindcss from 3.4.19 to 4.3.0#41dependabot[bot] wants to merge 1 commit into
Conversation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Bumps [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss) from 3.4.19 to 4.3.0. - [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.3.0/packages/tailwindcss) --- updated-dependencies: - dependency-name: tailwindcss dependency-version: 4.3.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/tailwindcss-4.3.0
branch
from
dac7941 to
6d07034
Compare
📝 WalkthroughWalkthroughThe ChangesDependency Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 66: Replace the incomplete Tailwind v3→v4 migration artifacts: in
app/globals.css replace the v3 `@tailwind` directives with the v4 import (use
`@import` "tailwindcss";), update the arbitrary CSS variable usage in the
DigitalEntity component (components/DigitalEntity.tsx) to use a standard CSS
custom property assignment (e.g., set --orbit-radius: value on the selector or
style rather than the old `[---orbit-radius:...]` arbitrary-syntax), and rename
all occurrences of the v3 utility flex-shrink-0 to the v4 utility flex-shrink in
components that use it (Button, SkillDetailsModal, PageHeader,
DeployAgentButton). After making these edits, run Tailwind's official upgrade
tool to apply any remaining automated changes and commit the migration changes
alongside the package.json version bump.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: da180889-89e9-4835-966a-559e9949c5e4
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json
| "postcss": "^8.5.8", | ||
| "serve": "^14.2.6", | ||
| "tailwindcss": "^3.4.19", | ||
| "tailwindcss": "^4.3.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "1) Old Tailwind directives still present?"
rg -n --hidden -g '!**/node_modules/**' '`@tailwind`\s+(base|components|utilities)\s*;' || true
echo
echo "2) v3 opacity utility patterns (removed in v4)?"
rg -n --hidden -g '!**/node_modules/**' '\b(bg|text|border|ring)-opacity-\d+\b' || true
echo
echo "3) Important modifier in prefix form (v4 expects suffix `!`)?"
rg -n --hidden -g '!**/node_modules/**' '(?:^|[\s"'\''])![a-zA-Z0-9_-]+' || true
echo
echo "4) CSS variable arbitrary value old bracket form (v4 expects parentheses)?"
rg -n --hidden -g '!**/node_modules/**' '\[[[:space:]]*--[a-zA-Z0-9_-]+' || true
echo
echo "5) Renamed utilities still used?"
rg -n --hidden -g '!**/node_modules/**' '\b(flex-grow-|flex-shrink-|overflow-ellipsis|decoration-(slice|clone))\b' || trueRepository: AIX-Format/GemClaw
Length of output: 7035
Tailwind v3→v4 migration incomplete; blocking issues found.
The version bump exists, but the codebase still contains v3-only patterns that will break styling in v4:
@tailwinddirectives inapp/globals.css(lines 1–3) — must be replaced with@import "tailwindcss";- Old CSS arbitrary variable syntax in
components/DigitalEntity.tsx:73—[---orbit-radius:...]form no longer supported flex-shrink-0utility used across multiple components (Button, SkillDetailsModal, PageHeader, DeployAgentButton) — renamed toflex-shrinkin v4
Run Tailwind's official upgrade tool and commit the migration changes before merging this version bump.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 66, Replace the incomplete Tailwind v3→v4 migration
artifacts: in app/globals.css replace the v3 `@tailwind` directives with the v4
import (use `@import` "tailwindcss";), update the arbitrary CSS variable usage in
the DigitalEntity component (components/DigitalEntity.tsx) to use a standard CSS
custom property assignment (e.g., set --orbit-radius: value on the selector or
style rather than the old `[---orbit-radius:...]` arbitrary-syntax), and rename
all occurrences of the v3 utility flex-shrink-0 to the v4 utility flex-shrink in
components that use it (Button, SkillDetailsModal, PageHeader,
DeployAgentButton). After making these edits, run Tailwind's official upgrade
tool to apply any remaining automated changes and commit the migration changes
alongside the package.json version bump.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| "postcss": "^8.5.8", | ||
| "serve": "^14.2.6", | ||
| "tailwindcss": "^3.4.19", | ||
| "tailwindcss": "^4.3.0", |
There was a problem hiding this comment.
This major version bump requires three companion changes that are missing from this PR:
tailwind.config.jsuses the v3 JavaScript config format, which Tailwind v4 ignores entirely. All custom colors (gemigram-neon,carbon-black, etc.), font sizes, animations, and keyframes defined there will silently stop being applied.app/globals.cssuses the v3 directives@tailwind base; @tailwind components; @tailwind utilities;— v4 replaces these with@import "tailwindcss";.postcss.config.mjsregisterstailwindcss: {}as the PostCSS plugin, but v4 moves this to@tailwindcss/postcss(already installed as a devDep). Without this change the PostCSS pipeline will fail to transform Tailwind utilities.
Merging this bump without those updates will break the build and strip all custom theme tokens from the UI.
|
إغلاق: هذا الـ PR قديم وسيتم فتحه من جديد مع rebase لاحقاً |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
1 participant
Bumps tailwindcss from 3.4.19 to 4.3.0.
Release notes
Sourced from tailwindcss's releases.
... (truncated)
Changelog
Sourced from tailwindcss's changelog.
... (truncated)
Commits
588bd734.3.0 (#20023)59936c6Addtab-*utilities (#20022)90a2373addzoom-*utilities (#20020)2e1ccf7Addscrollbar-gutter-*utilities (#20018)754e751Use non-existing example in tests (#20021)12eb5aeCleanup noisy test output (#20015)4255671Improve snapshot tests (#20013)8c77989Ensure math operators are surrounded by whitespace in arbitrary values (#20011)b4db3b9Add scrollbar-width and scrollbar-color utilities (#19981)08cad84Support--default(…)in--value(…)and--modifier(…)to support fallbac...Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for tailwindcss since your current version.
Summary by CodeRabbit
**Disclaimer This is AxiomID Review Agent.
Greptile Summary
This PR bumps
tailwindcssfrom v3.4.19 to v4.3.0, a major version upgrade that ships an entirely new CSS-first architecture and removes many v3-specific dependencies from the lock file.tailwind.config.js(JS-based config), the@tailwinddirectives inapp/globals.css, and the PostCSS plugin name inpostcss.config.mjsall need to be updated, none of which are included here.sucrase,postcss-nested,lilconfig, etc.) and also removesreact-hook-form/@hookform/resolvers, which were already absent frompackage.json.Confidence Score: 1/5
Not safe to merge — the app will fail to build and all custom theme tokens will be stripped from the UI until the config, CSS directives, and PostCSS plugin are updated for v4.
Three files outside the diff (tailwind.config.js, app/globals.css, postcss.config.mjs) are fundamentally incompatible with v4 and must be updated alongside this bump. Without those changes the PostCSS pipeline cannot resolve Tailwind utilities, the entire custom color/font/animation theme is silently dropped, and the build will error.
tailwind.config.js (v3 JS config ignored by v4), app/globals.css (@tailwind directives must become @import tailwindcss), and postcss.config.mjs (tailwindcss: {} must become @tailwindcss/postcss: {})
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A["package.json: tailwindcss ^4.3.0"] --> B{PostCSS Build} B --> C["postcss.config.mjs uses tailwindcss plugin"] B --> D["app/globals.css uses @tailwind directives"] B --> E["tailwind.config.js uses JS module.exports config"] C --> F["FAIL: v4 PostCSS plugin is @tailwindcss/postcss"] D --> G["FAIL: v3 directives unsupported in v4"] E --> H["FAIL: JS config silently ignored in v4"] F --> I[Build errors and broken styles] G --> I H --> IReviews (1): Last reviewed commit: "chore(deps-dev): bump tailwindcss from 3..." | Re-trigger Greptile